TylerQuinn saidfor example, I’m happy with language directories
Now lets say its a JS file you just make a simple de.js and store the strings in there?
and in my main file I’m including and using /lang/$site_lang/....
there’re a lot of users who has some websites in other languages (me for example ) and for these users it would be nice to have a translated version.
One of my first items on CC was the Simple Bulletin Board. And it was only in english. After some sales the buyers was asking for different language versions. I’ve build it and since these all my projects are equipped with multi-language support (shipped with de/en) – so everyone can translate the into prefered language in few files instead of searching and translating strings in every file (just copy language directory and translate).
daniyal saidI think not, ‘cause if you like a WordPress Plugin you need to get WordPress to use it, the same with Magento, ....
so would the original item/framework be included as a part of the download?
daniyal saidIt would be the same that an user purchased an Item from Author A and asked Author B (as freelancer) to make some upgrades to the Item and Author A wasn’t willing to do this. The User would have to pay $50-$100++ for this addon. And I don’t think Author A has an objection against the upgrade of Author B for the User. If Author B thinks it’s a good idea to build an Addon of the Item he would be able to offer it to the Marketplaye too for ~$3 or so – the Users don’t have to pay this little amount and Author B sells more of this addon, maybe.
would/should the original item’s license allow people building plug-ins on top of it?
1. If there’re are extended licenses of the addons the Author of the Main Item could by an extended license of the item and add it to the Main Item legally.
2. An Addon is highly depending on the Main-Item. What if the Main-Item was modified strongly and the Addon isn’t any longer working or that easy to include?
Official Versionizing of items (implicate other advantages too)
Addon with official relationship to Main-Item and Version
If the Main-Item was deleted or has an new (higher) Version-Number the Addon has to be soft-rejected ‘till it’s functionality was approved.
another BUTUpdates without Versionizing, Deletion of Main items, ...
just my thoughts
I think he has deleted some of his items.
Philo01 saidasked for this a couple of months ago, and it’s not allowed – had some ideas to protect my files from being stolen or illegal distributed
I wonder if it is allowed btw to encrypt certain files? So we could encrypt the core file of the system, so users can’t strip out the activation.
AND : even if we encrypt setup-scripts it would be not really difficult to decrypt the encrypted files, ‘cause the webservers work with the decrypted PHP -Code (just write the decrypted part into a new file or so ..) and then our items would be avail nulled on some other sites again :/
I think the addon category would be a nice idea,
- developers can create updates/addons for their items – makes sense for great updates of items
- I don’t really think, that the author of an addon should have the rights of the corresponding item, ‘cause if a buyer needs some modifications/addons he would hire a freelancer or… and have to pay much more – so the author of an addon could be the owner of the item or another one
I think it would be a nice feature, when we’re able to add a version number (float) to each of our items – I mean an additional field
and only if the version-number is changed a message on the buyers dashboard should appear, like Envatos Announcements (Payoneer, Secure password, ...)
that’s my thoughts – and I think this won’t be that hard to get realized
Totals: 23,622 34 23 $173.40bye
you could take a look to my portfolio too (image, forum and project management items there)