Guys, there seems to be quite a bit of confusion here! Let me try and clear it up.
LiveCode Community is free, open source, and lets you deploy to all platforms including HTML5. As we are all aware, you must share your source code for anything you make publicly available. LiveCode Indy offers two licensing options. You can license for Desktop/Mobile deployment and/or you can license for HTML5 deployment. These are separate purchases. You can add HTML5 to your Desktop/Mobile Indy for an additional cost. LiveCode Business, exactly as for LiveCode Indy, offers two licensing deployment options, Desktop/Mobile or HTML5. HTML5 is an addon for Desktop/Mobile, at additional cost. LiveCode Indy and LiveCode Community are separate installations, with different capabilities. To allow Indy to build "Community" standalones would involve some way of stripping out Indy features, removing passwords or encryption, ensuring no closed source addons were included... in short, its not a question of changing a button in the Standalone Builder. If you want to build open source licensed, free, Community edition standalones, then you need to use Community. I hope this helps... Regards, Heather Heather Laine Customer Services Manager LiveCode Ltd www.livecode.com > On 23 Jan 2017, at 11:08, Keith Martin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 22 Jan 2017, at 23:36, hh via use-livecode wrote: > >> Keith writes about the ability to make standalones, not about the license. >> I thought *every* edition of LiveCode can create HTML5 standalones? > > The Standalone Application Settings window in the standard Indy LiveCode does > show an HTML5 panel, but it also says "Your license does not include HTML5 > deployment entitlement." That's why I reinstalled the Community edition > alongside the Indy one. > > I don't know what the difference is between the Community edition's HTML5 > abilities and the Business edition, but it stands to reason that there is > something. :) Protecting/passwording code would make a lot of sense: not > locking code fits in with the general ethos of the open source Community > version, just as the ability to lock code is a significant benefit for those > publishing commercial products. I'd really like to see the vanilla version of > Indy given the Community level of HTML5 ability too rather than have to keep > another near-gig-sized app around just for that! :D > > k > > --- > > Keith Martin > Senior Lecturer, LCC (University of the Arts London) > Technical Editor, MacUser magazine (1997-2015) > http://PanoramaPhotographer.com > http://thatkeith.com > +44 (0)7909541365 > > --- > _______________________________________________ > 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
