Re: [Blog] Script Only Stacks

2016-03-24 Thread Dave Kilroy
cting to the line endings... - "The first 90% of the task takes 90% of the time, and the last 10% takes the other 90% of the time." Peter M. Brigham -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Blog-Script-Only-Stacks-tp4701942p4702591.html Sent from

Re: [Blog] Script Only Stacks

2016-03-04 Thread Tim Bleiler
Thanks Mark!! Sorry to take up everyone’s time on that, but good to know I guess. Tim > On Mar 4, 2016, at 10:22 AM, Mark Waddingham wrote: > > On 2016-03-04 16:12, Tim Bleiler wrote: >> Thanks Mark, >> I submitted the file in bug report 17067. >> Tim > > Okay - so - the problem with that fi

Re: [Blog] Script Only Stacks

2016-03-04 Thread Mark Waddingham
On 2016-03-04 16:12, Tim Bleiler wrote: Thanks Mark, I submitted the file in bug report 17067. Tim Okay - so - the problem with that file is that your text editor has decided to be nice and convert normal double-quote " to appropriate paired quotes. Your file has: script “MyTest” Rat

Re: [Blog] Script Only Stacks

2016-03-04 Thread Tim Bleiler
Thanks Mark, I submitted the file in bug report 17067. Tim > On Mar 4, 2016, at 5:38 AM, Mark Waddingham wrote: > > On 2016-03-03 20:45, Tim Bleiler wrote: >> It probably doesn’t matter much as long as it’s made clear what >> encodings are allowed. I would guess most users taking advantage of

Re: [Blog] Script Only Stacks

2016-03-04 Thread Tim Bleiler
Thanks Jim, Since you aren’t having the problem I tried a couple of other things. First, I had been dragging the file to the Livecode icon in the dock, so I tried opening it through the menu as you had done but I still get a file is not a stack message. I then shut my whole system down and trie

Re: [Blog] Script Only Stacks

2016-03-04 Thread Mark Waddingham
On 2016-03-03 20:45, Tim Bleiler wrote: It probably doesn’t matter much as long as it’s made clear what encodings are allowed. I would guess most users taking advantage of this feature could live with that. Casual users may be confused however, because most of us don’t give much thought to such d

Re: [Blog] Script Only Stacks

2016-03-04 Thread Mark Waddingham
On 2016-03-03 19:43, Robert Mann wrote: I guess you checked that the first line is not empty and that there is no space before the first line? "script" must be at the beginning of first line. Engine is very pick at that. And sometimes the engine/ide adds another line at top, leading to 2 line

Re: [Blog] Script Only Stacks

2016-03-03 Thread Peter TB Brett
On 03/03/2016 18:12, Peter TB Brett wrote: On 03/03/2016 17:48, Tim Bleiler wrote: In the blog post, Mark states that "The fact that script only stack files really are just text files is really important! It means you can edit and create them in any text editor you choose, and use any text based

Re: [Blog] Script Only Stacks

2016-03-03 Thread Peter TB Brett
On 03/03/2016 18:59, Peter Bogdanoff wrote: It would seem that script-only stacks would not be able to be locked—have the password property set. This would seem to be a limitation for commercially-released projects with library stacks, unless they are a substack of something else. Yes, that'

Re: [Blog] Script Only Stacks

2016-03-03 Thread Jim Lambert
> TimB wrote: > If I open one up in TextEdit and save it, Livecode gives me the error > message: “Unable to open stack: File is not a stack”. Hi Tim, I’m not seeing that here with LC 8.0 (dp 15) 1. Launch TextEdit 2. File > New 3. Format > Make Plain Text 4. type script "test2" on openstack ans

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
It probably doesn’t matter much as long as it’s made clear what encodings are allowed. I would guess most users taking advantage of this feature could live with that. Casual users may be confused however, because most of us don’t give much thought to such details; a text file is a text file. Mar

Re: [Blog] Script Only Stacks

2016-03-03 Thread Monte Goulding
That is indeed the use case I used to justify the inclusion of the property when I contributed it. The other one was a quick way to convert an existing stack to scriptOnly without copy and paste. There was some discussion if we should add the property due to the risks to stack content when setti

Re: [Blog] Script Only Stacks

2016-03-03 Thread Monte Goulding
I know I have discussed this with Mark Waddingham before. I believe he was originally thinking of allowing other encodings at some point but was not averse to my suggestion of only supporting UTF8 with or without BOM. Sent from my iPhone > On 4 Mar 2016, at 6:17 AM, Tim Bleiler wrote: > > I g

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
> On Mar 3, 2016, at 1:59 PM, Peter Bogdanoff wrote: > > It would seem that script-only stacks would not be able to be locked—have the > password property set. > > This would seem to be a limitation for commercially-released projects with > library stacks, unless they are a substack of someth

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
> On Mar 3, 2016, at 2:01 PM, Tore Nilsen wrote: > > I think TextWrangler is a better choice than TextEdit for this purpose. In > textWrangler you can specify both UTF 16 and Unix line endings. > TextWrangler shows a working script only stacks as UTF-8, with BOM and Unix (LF). A “broken” on

Re: [Blog] Script Only Stacks

2016-03-03 Thread Robert Mann
t; so in the erasing process, by hand.. things can happen. Robert -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Blog-Script-Only-Stacks-tp4701942p4701956.html Sent from the Revolution - User mailing list archive at Nabble.com. ___

Re: [Blog] Script Only Stacks

2016-03-03 Thread Richard Gaskin
Tim Bleiler wrote: >> On Mar 3, 2016, at 1:38 PM, Richard Gaskin wrote: >> >> I wonder if it needs to use LC's native line ending, ASCII 10, >> rather than ASCII 13 that many Mac tools use. > > Thanks Richard, > > First, do you know of way to set this in TextEdit? I don’t see > anything that can

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tore Nilsen
I think TextWrangler is a better choice than TextEdit for this purpose. In textWrangler you can specify both UTF 16 and Unix line endings. Tore > 3. mar. 2016 kl. 19.57 skrev Tim Bleiler : > > > >> On Mar 3, 2016, at 1:38 PM, Richard Gaskin >> wrote: >> >> I wonder if it needs to use LC's n

Re: [Blog] Script Only Stacks

2016-03-03 Thread Peter Bogdanoff
It would seem that script-only stacks would not be able to be locked—have the password property set. This would seem to be a limitation for commercially-released projects with library stacks, unless they are a substack of something else. Peter Bogdanoff UCLA > On Mar 3, 2016, at 8:12 AM, Steve

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
> On Mar 3, 2016, at 1:38 PM, Richard Gaskin wrote: > > I wonder if it needs to use LC's native line ending, ASCII 10, rather than > ASCII 13 that many Mac tools use. Thanks Richard, First, do you know of way to set this in TextEdit? I don’t see anything that can change that. Second, if tha

Re: [Blog] Script Only Stacks

2016-03-03 Thread Matt Maier
I was just reading that the line endings can be different (because of course they can). http://www.hyperactivesw.com/cgitutorial/scripts1.html#trouble *Make sure line endings in scripts are correct for the server platform. DOS line endings are carriage return and linefeed. Unix line endings are a

Re: [Blog] Script Only Stacks

2016-03-03 Thread Richard Gaskin
Tim Bleiler wrote: Thanks Peter, I gave that a try and I still get the same message. My attempts to create them from scratch were saved as UTF-8 and I’ve tried all the other options in TextEdit as well. I have noticed that if I open a functioning script only stack in ATOM it is identified a

Re: [Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
Thanks Peter, I gave that a try and I still get the same message. My attempts to create them from scratch were saved as UTF-8 and I’ve tried all the other options in TextEdit as well. I have noticed that if I open a functioning script only stack in ATOM it is identified as UTF-8. Tim > On

Re: [Blog] Script Only Stacks

2016-03-03 Thread Peter TB Brett
On 03/03/2016 17:48, Tim Bleiler wrote: In the blog post, Mark states that "The fact that script only stack files really are just text files is really important! It means you can edit and create them in any text editor you choose, and use any text based processing tool on them…” I’ve been tryi

[Blog] Script Only Stacks

2016-03-03 Thread Tim Bleiler
In the blog post, Mark states that "The fact that script only stack files really are just text files is really important! It means you can edit and create them in any text editor you choose, and use any text based processing tool on them…” I’ve been trying to work with script only stacks on Mac

Re: [Blog] Script Only Stacks

2016-03-03 Thread dunbarx
Whoa, Stacks can now be behavior references? Now that is terrific. Craig Newman -Original Message- From: Steven Crighton To: use-livecode Sent: Thu, Mar 3, 2016 11:14 am Subject: [Blog] Script Only Stacks Dear List In LiveCode 8 there is a new option in the (new) 'New

[Blog] Script Only Stacks

2016-03-03 Thread Steven Crighton
Dear List In LiveCode 8 there is a new option in the (new) 'New Stack' submenu: Script only Stack. Mark has just published a blog post on this very subject https://livecode.com/script-only-stacks/ Looking forward to hearing your comments.