Plain text library stacks

[Michael Doub]

Mark,   It appears that when you programmatically create a script only 
stack and save it.  The engine auto inserts the first line: script 
"stackname".    I see that when I look at the file with a text editor.   
When I edit the script of the stack in livecode the script "stackname" 
line is missing.

Will there be any problems if there are two script "stackname" 
statements in the text file.  This could occur if the user adds it when 
in the livecode editor.

What is the recommended method for determining if a stack is a "script 
only" stack?

Thanks
    Mike


On 4/23/15 1:08 PM, Mark Waddingham wrote:
> 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.
>
> Mark
>
> 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.
>>
>> 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 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.
>>>
>>> --
>>> 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:
>>> 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
> _______________________________________________
> 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
>