Differences between Commercial and Community versions of LiveCode

Tom Glod tom at makeshyft.com
Tue Jun 5 17:24:33 EDT 2018


hmmmm..... maybe i'm thinking all the way back to v6 or v7 standalones. cuz
v8 is also not visible.

On Tue, Jun 5, 2018 at 5:20 PM, Tom Glod <tom at makeshyft.com> wrote:

> so i went to check the standalone file from v9 ...and indeed the code
> cannot be seen.  in previous versions, I could clearly see the script text
> of a stack by opening it up in notepad++.....
>
> maybe i was hallucinating...... but i'm pretty sure i checked this before
> because of my own curiosities about this subject. can anyone confirm this
> change?
>
>
> On Tue, Jun 5, 2018 at 3:49 PM, Brian Milby via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> I believe this thread started as a result is someone asking if there was
>> a way to recover their work if all they could salvage was a built binary
>> (from community edition). It sounds like there should be a way based on
>> another response in the thread.
>>
>> Thanks,
>> Brian
>> On Jun 5, 2018, 2:16 PM -0500, Richard Gaskin via use-livecode <
>> use-livecode at lists.runrev.com>, wrote:
>> > Richmond Mathewson wrote:
>> >
>> > > Recently I ran off a very simple standalone with the Indy and the
>> > > Community version of LC 8.1.9
>> > > and cracked both of them open with a text editor.
>> > >
>> > > In neither of the standalones could I access the code.
>> > >
>> > > Presumably this means that a standalone generated with the Community
>> > > version cannot be
>> > > reverse-engineered in such a way that its original code can be read?
>> >
>> > Binding the stack to the runtime engine makes the source difficult to
>> > access, and the objects impossible to modify.
>> >
>> > The requirement of GPL-governed works is that source code is available
>> > in a form that allows modification.
>> >
>> > I would not imagine requiring end-users to sift through bits of a binary
>> > executable would satisfy any definition of GPL compliance.
>> >
>> > Either the source stack files are made available to any user of the
>> > executable who wants them, or the entity distributing the executable is
>> > in violation of LiveCode Ltd's copyright.
>> >
>> > --
>> > Richard Gaskin
>> > Fourth World Systems
>> > Software Design and Development for the Desktop, Mobile, and the Web
>> > ____________________________________________________________________
>> > Ambassador at FourthWorld.com http://www.FourthWorld.com
>> >
>> > _______________________________________________
>> > 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
>>
>
>



More information about the Use-livecode mailing list