Plain text library stacks
mark at livecode.com
Thu Apr 23 13:08:52 EDT 2015
That is something to be aware of.
The purpose of a script only stack is to be text on disk... Password protection requires binary output, so in that case you might as well just use a normal stack.
Sent from my iPhone
> On 23 Apr 2015, at 17:49, Peter Haworth <pete at lcsql.com> wrote:
> Not sure if this is a problem or not but it appears that any password I set
> on the stack isn't retained. If I remove the stack from memory and re-open
> it, the password isn't retained. I guess just something to be aware of
> rather than a problem.
> 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 23, 2015 at 9:26 AM, Mark Waddingham <mark at livecode.com> wrote:
>> So, script "stackname" must be at the 1st line of the textfile.
>> Ah yes - that is indeed the case - it is quite picky, for two reasons.
>> The first was that the main use-case I had in mind when implementing it
>> was to replace IDE stacks which were only scripts and thus they would be
>> edited in the IDE.
>> The second is that the *only* part of the file which the engine retains
>> when it is loaded is the 'name' on the first line and everything on the
>> second line onwards. If text before the 'script' line were allowed then it
>> is not clear how you might access that when the stack is loaded into memory
>> - it would essentially be invisible information in the internal stack
>> structure that would only appear when the stack is saved again.
>> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
>> LiveCode: Everyone can create apps
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode