There's something worth adding to this. It is not necessary for, say, a tools plugin in the IDE to go dual licensed. Because stack protection is only in the commercial version you'd have to have no protection on stacks for community edition users (and thus it's probably not worth having any on your commercial version either). While that means people can get at the source code, it doesn't mean you have to give them the right to redistribute it.
You can sell people a tool with a license that allows them to use it in commercial or community editions of LiveCode - as long as they don't distribute that (or any part of it) with community edition projects there's no problem with them mixing with the GPL'd code on their own systems. If your tool generates code it's a good idea to make it explicit in your license that code it generates may be licensed under some GPL compatible OSS license. Of course if you sell a plug-in that is included in final apps (components, externals etc) then that will have to go dual licensed to be available to community edition users. Mark ________________________________ From: Malte Brill <revolut...@derbrill.de> Well, it is in the nature of the GPL license that you can not keep code closed. Otherwise it would not be free. Now it is up to the plug in makers to either follow runrevs lead and go Dual Licensed too (which quite a few, me included already comitted to), or if they keep their add ons closed and just cater the commercial market. I am pretty convinced that the whole OSS thing will work out in a big way regarding add ons. over the course of the next 2 years I hope to see many many add ons becoming available, either OSS or Commercial or both. animationEngine already is available in a non protected version, I just need to give the mothership time to breathe to update it on the marketplace server. Until then the open version can be found here: http://derbrill.de/animationEngine5.0.2.zip Still there are license requirements to be met with the release (you can find those in the stack script) For the plugins you are using, I guess it will be best to ask the vendors directly what they are planning to do. All the best, Malte _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
