Project Browser vs App Browser (was "script scope variables inexplicably becoming unset")

[Kay C Lan]

On Mon, Jan 5, 2015 at 1:18 AM, Peter Haworth <pete at lcsql.com> wrote:

>
> Community Edition can't load password protected stacks because that would
> break the rules of open source,


That is not my understanding of the situation. There is no reason why an
OSS liscensed app can't interact with Closed Source Software. There is
nothing preventing Linux users from using CSS:

https://en.wikipedia.org/wiki/List_of_proprietary_software_for_Linux

My understanding is the real reason is a technical Catch-22 hurdle that
Runrev can't cross. To include the code that would open your Password
Protected Stack means that the 'password protection code' needs to be in
the LC Community Edition, which means it then has to be Open for anyone to
look at due to the OSS License, which means anyone can figure out how the
Commercial Edition secures stacks. No one would buy LC Commercial once they
realise anyone with a Community Edition can open their product and steal
all their code.

So to keep the Commercial Edition secure, the password protection code can
not be included in the Community Edition which means that whilst the
Community Edition can use any other CSS extensions/software, it
embarrassingly can't use extensions written in it's own LiveCode Commercial
Edition.

So nothing to do with the OSS license directly but everything to do with
keeping LC Commercial a viable and secure money maker.