OSS vs INDY Comparison?

[dvenus]

Hi!

Is there a list or chart that compares the OSS version to the Indy version?

Thanks,

Dave

[shaosean]

The only thing I could find is the differences between the Indy and the Enterprise licenses..
https://livecode.com/products/livecode- ... m/pricing/

I think the community just can't compile, plus all your code is automatically GPL'd (which is the biggest reason I won't use it)

[AxWald]

Hi,

further down the page Shaosean linked is a comparison chart. Even if it doesn't explicitly show the community edition you can filter out your data there.

Community edition compared to Indy:

• No closed source license, enforces GPL V3
• No iOS support, due to Apple not allowing GPL software in their iJail
• No included 3rd party addons (Extension pack)
• No advanced networking features
• No built-in source code protection
• And for sure, no RunRev support

Hope this helps :) Have fun!

[FourthWorld]

Hi Dave -

To be clear, script compilation and delivery of standalone applications are fully functional in LiveCode Community Edition. In fact, nearly all of the several thousand language features of LiveCode are available across all editions, including Community.

As Ax noted, LiveCode Community Edition is licensed under the GPLv3, so like all programs that use that most popular open source license, any derivative works distributed to others will inherit the rights and responsibilities of that license.

Open source software is of course distinguished by having source code available. The GPL is a good choice for licensing software where you want downstream users to also enjoy the freedom of access to source code.

And being dual-licensed, for any other goals proprietary licenses of LiveCode are also available.

Many extensions in the LiveCode ecosystem are dual-licensed so they can be used in either he GPL-governed Community Edition, or the Indy or Business editions.

There are a few exceptions, such as the third-party networking external now bundled with LC 9 Indy and Business editions. The developer of that external chose a license which is not compatible with the GPL, so LiveCode Ltd. can only distribute it with non-GPL editions. That said, the core language functions for HTTP, FTP, and socket support cover such a wide range of uses cases conveniently that I've not yet needed anything specific to the new advanced networking options provided in the tsNet external.

That said, anyone can produce extensions for LiveCode which are GPL-compatible, or even exclusively GPL, for use with the Community Edition. I have one project on the horizon for which we may deliver libraries for LC under GPL license only, to encourage free and open use.

The mechanism in the proprietary editions of LiveCode for password-protecting source code is of course unavailable in the Community Edition, as it wouldn't make logical sense to prevent users from having access to source code when distributing works under he GPL which explicitly guarantees access to source code.

Support for the Community Edition is provided by the community. This forum and many other venues exist to help ensure everyone using LiveCode can learn to use it well.

Beyond these differences, most of what LiveCode delivers is available with complete parity whether you want to make open source software with the Community Edition or proprietary works with the Indy or Business editions.

[dvenus]

Thank you to all who replied! I have a better understanding of the different editions. Dave