Re: Store script as run only
Re: Store script as run only
- Subject: Re: Store script as run only
- From: "Gary (Lists)" <email@hidden>
- Date: Fri, 07 Apr 2006 16:22:42 -0400
"Jens Eliasson" wrote:
> Because I don't want to risk this [overwriting script code with a read-only
> version] to happen again. So is there a way to shed the source code while
> resaving a script, preferably not scripting the SE?
One suggestion involves using Smile as your script editor.
With Smile, there are a number of user-friendly and Gary-proof options.
1. Use the AppleScript windows (plain text windows) of Smile to develop and
save your script, then make only the kind of output copy you want, when you
want (complied script, application, stay-open, run-only, self-writing,
no-work, etc.)
2. Getting a bit more sophisticated, you can write your own permanent
handler for Smile, applicable to only you or to everyone, so that when you
_do_ save a script, your permanent handler will be invoked and divert your
save action to your own process [preventing you from over-writing, or
whatever else you want.]
3. Build your Project Launcher Smile Dialog. Mine works like this:
I open my Working Projects application (a Smile dialog bundle).
This presents my list of working projects.
I can drag new folders to this dialog, thereby adding them to the
Working Project List. (I can even title them differently from
the folder I just dragged, but I mostly just use the folder name.)
Or, I can double-click one to open that project. This triggers a
sequence of actions: The 'versions' [1] folder inside my project
folder gets 'zip compressed' and then copied to an external USB.
This takes a few seconds.
Then, the Finder activates and my folder is opened for my work
session. If I botch things, then I've only lost that particular
session of work, and the off-disk (well, off my main drive) zip
copy is available (yes, from my Smile dialog ;)
[1] My project folders are all structured exactly the same, by the way. With
the assistance of Ben Waldie, a couple of years ago, I worked out a folder
structure strategy that works for me -- for my projects -- and one that
works well for outside (paid) projects. This same-structured system has
served me well, because it allows both easy automation as well as consistent
"human memory" triggers of where things are, what I should be doing and all
the like (seeing a 'Backups' folder inside a working folder is such a
trigger.)
Cheers,
--
Gary
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden