• View
• Edit
• History
• Print
• Backlinks

FAQ

1.  How do I contribute code to the platform?

You contribute via Github, please see our contributors guide. Similar to other dual license open source projects, we require you to assign copyright for any patches back to us.

You are also free to create your own version of the platform and modify it in any way you choose without submitting the contributions back to us. Any version fork must also be made available under the terms of the GPL.

2.  Do I need a Commercial License to allow users to test my Closed Source App?

Having people download and test the your app counts as distribution. If you are distributing a standalone executable app, under the terms of the GPL you must provide the source to those that are downloading the app.

Essentially, if you don’t want to share your source code, you need a commercial license.

3.  My App uses code running on a server in order to work, do I need to publish that code as part of the app?

If your code on the server is an integral part of making your LiveCode based software work then it is linked with the app, and forms a part of the code you must release if you are using LiveCode Community. This would apply in the same way if you were using LiveCode as a front-end to a command-line utility, linking it via shell().

In general, if any part of your app is released under the GPL license, all of it needs to be GPL, you cannot mix open and closed source in your app. Otherwise, you have to use livecode commercial.

4.  Can you explain your dual license policy?

A dual license provides more than one license type to use LiveCode. In addition to the free and open GPL version, commercial license types are available to enable the creation and distribution of closed source software applications and for technical support.

You don’t need to purchase a license until it is time to redistribute your app, you can build it first using the Community Edition.

The commercial version is available as an annual subscription, either Indy or Business. A single license includes the ability for a single developer to create and build unlimited applications then distribute them royalty-free on all supported platforms. Unlike the open source version, it does not include access to the source code. It includes the script password security module which provides an additional level of protection for your code. It removes the requirement to redistribute the source code of your application when you come to redistribute it. If your subscription expires any applications built will continue to run but you will not be able to create new closed source applications or updates to existing applications until you renew your commercial license.

5.  Can I sell the open source software I create with the open version of LiveCode?

Yes. You are free to sell or commercialize anything you create under any business model you choose. For example you could sell your application, or give it away for free and charge for service and support. You must include the complete source code for your software with any software you sell and you cannot prevent a customer redistributing that source code. To protect your intellectual property you need a commercial license for LiveCode.

6.  Is this demoware?

No. The entire core platform (excluding script security) is included in the open source version. A commercial license is required to produce closed source commercial software, or to obtain additional benefits such as training materials or technical support from LiveCode Ltd.

7.  Is HTML5 export included in free community version?

Yes, it is. The community version always add a link to download the source of your code. The HTML commercial version is needed just for closed source project.