Re: [ANN]Reading uncompiled scripts from ASE in Mountain Lion
Re: [ANN]Reading uncompiled scripts from ASE in Mountain Lion
- Subject: Re: [ANN]Reading uncompiled scripts from ASE in Mountain Lion
- From: Shane Stanley <email@hidden>
- Date: Wed, 08 Aug 2012 23:45:11 +1000
On 08/08/2012, at 10:41 PM, Chris Page <email@hidden> wrote:
> Since one should compile and run scripts before sharing them with others, it should be unlikely that one will unknowingly distribute scripts with uncompiled source changes.
Stuff happens. It's like saying that since one should keep backups, it is unlikely that anyone will ever lose any data. And Murphy's Law means it's likely to happen at the worst possible time.
I also think you're overlooking the fact that some users are going to see, and use, the ability to save uncompiled scripts as a feature. Can't get a script finished? No longer do you have to keep fiddling, or do a .applescript save-as -- you can just save uncompiled, or shutdown or quit. I mean, if users have to worry about the state of a document and how they save it, aren't you going against what the whole new document model is supposed to be about?
So I think it will take time, but as people get used to it there are likely to be more uncompiled documents floating around. Then the potential for normal mistakes will kick in, because the difference can't be seen without actually opening a script, which usually means launching any apps it uses, etc, etc.
> If it occurs on a regular basis we need to know about it.
It doesn't have to happen often to ruin someone's day.
Maybe I'm wrong. Maybe it will never happen to anyone, and I've wasted my time writing a utility that no-one will ever need. But I think it's better to be on the safe side, rather than waiting to see if enough people are getting bitten. And I think it's important that people know of the issue, and understand it.
> If you're concerned that you may have made source changes, simply Compile, Run, or Save the script before sharing it, as usual.
One of the problem areas, though, is documents saved automatically when ASE is quit. You seem to assume that completion of a script and deployment are roughly contemporaneous -- that's not always the case.
FWIW, I think the problem could be reduced by the use of different icons, to reflect the compiled status.
> (An explicit Save compiles a script, as usual.)
In my tests it *tries* to compile, but will still save -- and even export execute-only -- uncompiled.
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden