Spot on! Thanks Jacqueline, That is exactly the choice I have : 1. make a viewer of a special kind of media aggregate with the community version under GPL & deliver these media aggregate in a separate file under whatever license. (plus i'll document that format so that others can produce such content)
--> I can crunch in a specialized in house editor --> content will be more "industrialized" not as rich visually, just like an app instead of the original hypercard spirit mix of app + book. --> not ok for iOs distribution 2. create fully contained mixed apps+content in the spirit oh hypercard, non GPL, with livecode commercial edition. --> ok for iOs distribution to which I add : 3. have a tier party do the viewer ready for iOs and let me concentrate on the in house editor. --> ok for iOs distibution 4. switch to web service for distribution which is something I do "master" thanks to revIgniter bootcamp and some in house development i've done in that view. --> ok for wider usage/distribution --> if third parties/individuals wish to produce content, I can either open source the in house editor or sell it with a commercial version. 5. see in the future if live code HTML5 can help produce better quality content for the web, that would match the quality of interaction we once upon a time had with hypercard stacks! And the winner is : number 4 (the web app path) considering that for kids, having to install one more app on a phone is to my point of view not ideal. Also dealing with separate content is subject of problems on my android phone. So as conclusion, the "evolution" from the hypercard time is internet, web pages, web apps. bye bye stacks. So that is it for the issue number 3 for me // many thanks all and I hope it can help others have a clearer view of the impact of licensings schemes in their plans. RObert -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Open-source-closed-source-and-the-value-of-code-tp4701649p4701848.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ 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
