multi-line constants? (for RSA keys)

Peter Haworth pete at lcsql.com
Fri Apr 4 04:08:59 CEST 2014


I think the real solution is to store persistent values in a file or a
database.

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 Thu, Apr 3, 2014 at 5:50 PM, Bob Sneidar <bobsneidar at iotecdigital.com>wrote:

> Thanks, I think I remember what the issue was now. If you want your stacks
> to be writable, they cannot be part of the app. Is that correct? So if the
> application has the need to save things like persistent properties and
> such, you HAVE to  separate the substacks, thereby making them runnable in
> the IDE.
>
> So the only real solution it seems to me is to password protect all the
> substacks before compiling, and then write code into the stacks to prevent
> them from running if they are the topStack of themselves.
>
> Bob
>
>
> On Mar 31, 2014, at 10:37 , J. Landman Gay <jacque at hyperactivesw.com>
> wrote:
>
> > On 3/31/14, 10:10 AM, Bob Sneidar wrote:
> >> It was my impression that the mainstack gets*glued*  together with
> >> the runtime engine and is not accessible in the same way the
> >> substacks are, which are merely included in a subfolder or in the
> >> case of OS X, in the package. Is this no longer the case? Or have I
> >> simply misunderstood all this time?
> >
> > If the substacks are true substacks, they are "glued" to the engine the
> same way the mainstack is. This is the standard way substacks work. All
> stacks in a standalone are part of the same file on disk and received the
> same protection.
> >
> > However, there is a checkbox in standalone settings that allows you to
> save out substacks as separate files during the build. If you choose to do
> that, then they are no longer substacks, they are removed from the file and
> turned into individual document stacks. Those are the same as any other
> stack you'd use during development and as such, they are no longer part of
> your app. They're just loose in the folder (or in the bundle on Macs) and
> can be opened by anyone with a copy of LiveCode, no tricks required. The
> scripts will be obscured if the stack is password protected but everything
> else, including properties, will be accessible because it's just a plain
> old stack now.
> >
> > So if you want the same protection you'd get in the mainstack, just make
> sure you don't have that checkbox selected.
> >
> > --
> > Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> > HyperActive Software           |     http://www.hyperactivesw.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