Re: Conditional compile

2013-04-04 Thread Peter Haworth
On Thu, Apr 4, 2013 at 5:43 PM, Dr. Hawkins wrote: > You don't need to make your free version open source; just compile it > with the commercial product like the other one. > This isn't a compiled standalone, it's a plugin. Pete lcSQL Software ___

Re: Conditional compile

2013-04-04 Thread Dr. Hawkins
On Thu, Apr 4, 2013 at 11:04 AM, Peter Haworth wrote: > I'm struggling with the best way to deal with the codebase for this > situation. I can set a custom property to define which version I'm in but > since I can't password protect my source code in the open source version, > it would be a simp

Re: Conditional compile

2013-04-04 Thread Peter Haworth
On Thu, Apr 4, 2013 at 3:08 PM, J. Landman Gay wrote: > Heh. :) More seriously: > > get the password of stack "home" > > It's locked right now and will return "true". > No too serious though... is it? Surely there'll be an official way to check, like maybe another value for the environment or s

Re: Conditional compile

2013-04-04 Thread Peter Haworth
On Thu, Apr 4, 2013 at 2:42 PM, Mark Wieder wrote: > I do something similar to implement plugins in an app: check a specific > directory, get a list of the stacks there, query the interface of each one > (the uRIP["events"]) and enable those features. > I like that! > > > I probably missed this

Re: Conditional compile

2013-04-04 Thread J. Landman Gay
On 4/4/13 4:42 PM, Mark Wieder wrote: Peter Haworth writes: I probably missed this somewhere but how can we check in a script if we're running in the open source version of Livecode? if the date > 2013.04.09 then ... Heh. :) More seriously: get the password of stack "home" It's locked

Re: Conditional compile

2013-04-04 Thread Mark Wieder
Peter Haworth writes: > 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 ba

Re: Conditional compile

2013-04-04 Thread Peter Haworth
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 somew

Re: Conditional compile

2013-04-04 Thread Mark Wieder
Peter Haworth 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 int