Thanks Mark. I was thinking of something similar to that after I wrote the
email.  Actually revolving around a library stack to make the calls a
little easier.  Would mean some reorganization of the code but I think it's
pretty well modularized so probably not too bad.

I probably missed this somewhere but how can we check in a script if we're
running in the open source version of Livecode?

Pete
lcSQL Software <http://www.lcsql.com>


On Thu, Apr 4, 2013 at 12:17 PM, Mark Wieder <[email protected]> wrote:

> Peter Haworth <pete@...> writes:
>
> > Am I faced with maintaining two separate stack files?  Or perhaps some
> sort
> > of release process that would assemble a stack file from various
> components
> > so I only have to duplicate the things that differ between the two
> versions?
>
> Can you put the extra functionality into a substack or a substack file?
> Then
> in your main stack (probably on preOpenstack) check for the existence of
> the
> substack and take things from there. Disable calls into the substack if it
> isn't there, disable menu items that would call into it...
>
> --
>  Mark Wieder
>  [email protected]
>
>
>
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to