Licensing

Simon Smith hello at simonsmith.co
Tue Jan 6 16:09:47 EST 2015


Hi

While I don't have have much experience with the LiveCode GPL, I have spent
some time looking at how the GPL is used with systems, so not certain with
how this would translate

On Tue, Jan 6, 2015 at 8:52 PM, Peter Haworth <pete at lcsql.com> wrote:

> Hi Bill,
> Thanks for the input.
>
> I think I'm homing in on how to do this.
>
> My web site will have 3-4 videos on the main features of the product and
> also the User Guide.
>
> User buys the product and gets either a download link and maybe a license
> key as Mark suggested.
>
> I have a license agreement in my SQLiteAdmin program that with a few minor
> alterations will work for lcStackBrowser.
>
> I already have an installer stack and will make that into a standalone
> which has the license agreement built into it.  When the installer runs for
> the first time, it will display the license agreement and note that by
> installing they are accepting its terms.
>
> I'll also put the license agreement into the main stack script although
> anyone would be able to remove it.  And just for kicks, I'll put it into a
> file on my web site and provide a way to display it from the product.
>
> Yes, I know this is somewhat paranoid but it makes me feel comfortable
> enough that I think I'm ready to make things available for the Community
> Edition.
>
>
>
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
>
> On Mon, Jan 5, 2015 at 7:48 PM, Bill Vlahos <bvlahos at mac.com> wrote:
>
> > In this case the software in question (like my lcTaskList) is a tool for
> > use in the IDE not a library or object that would be included in a
> product
> > made with LiveCode.
> >
> > There is no way to tell if this software is written in the Community
> > Edition vs. the Commercial Edition. If the program was password protected
> > you would know it could only be created and used in the Commercial
> Edition.
> > The differentiator in this case is the lack of password protection which
> > allows the plugins to work in either edition.
> >
> > I have a copyright notice in lcTaskList so the work is protected against
> > copyright violation even though the source code is visible in the same
> way
> > as books are visible yet copyrighted. It is not free nor can it be sold
> or
> > distributed to other people.
> >
> > Making different versions of the software makes sense in some
> > circumstances but that is more commonly done with making a demo or trial
> > version that has limitations. In the case of lcTaskList there is only one
> > version which works and costs the same for both versions. Buying it is
> just
> > like buying any other software. As Peter pointed out there just isn’t any
> > way to make a trial version of software that works in the Community
> Edition
> > unless the trial version is different than the release version. Since
> this
> > type of a trial version is feature limited the user doesn’t really know
> all
> > the things the program can do.
> >
> > One way to help customers is to offer a money back guarantee (lcTaskList
> > does through the LiveCode Store).
> >
> > Bill Vlahos
> > _________________
> > InfoWallet (http://www.infowallet.com) is about keeping your important
> > life information with you, accessible, and secure.
> > lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
> > RunRev lcTaskList Forum: (http://forums.runrev.com/viewforum.php?f=61)
> >
> > > On Jan 5, 2015, at 5:23 PM, Andrew Kluthe <andrew at ctech.me> wrote:
> > >
> > > No, I think it would have to use the same license as livecode in this
> > > situation as all applications made with community edition are required
> to
> > > comply as well. Unless, runrev makes an exception and allows you to run
> > > non-gpl plugins in their gpl ide (stacks made by commercial version but
> > > used in the community version?).
> > >
> > > Seems like a lot of people solve this by making the commercial version
> > have
> > > more current feature sets or better support than the community
> editions.
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 

*Simon Smith*
*seo, online marketing, web development*

w. http://www.simonsmith.co
m. +27 83 306 7862



More information about the Use-livecode mailing list