Re: Migrating scripting additions to Mac OS X
Re: Migrating scripting additions to Mac OS X
- Subject: Re: Migrating scripting additions to Mac OS X
- From: Brennan Young <email@hidden>
- Date: Wed, 27 Jun 2001 07:11:10 +0200
- Organization: Magic Lantern
>
Subject: Re: Migrating scripting additions to Mac OS X
>
From: JJ <email@hidden>
>
To: applescriptmaillist <email@hidden>
>
Look at this I.e. (it's easy)
>
>
tell app "Quark"
>
tell document 1
>
tell paragraph i of selection
>
set the_word to word 1
>
tell app "Akua Sweets"
>
set new_word to (transcribe the_word as upper cased)
>
tell app "Finder"
>
set the_store to alias "HD:myfile"
>
tell app "Jon's Commands"
>
if fileIsBusy the_store = false then
>
tell app "Finder"
>
write new_word to the_store
>
end tell
>
end tell
>
end tell
>
end tell
>
end tell
>
end tell
>
end tell
Ugh.
Don't forget that your most valuable resource is your attention span. Having to
keep an extra half dozen extra 'end tells' in my mental stack strikes me as a
serious waste. Well, I also know this could have been constructed differently
without all the nesting.
I must admit, there would be some advantage in being able to explicitly use
terminology from a given OSAX, to avoid name-space collisions and be more
structured, but I can understand why people don't like the idea.
What about some way of explicitly loading and unloading OSAXen? I know this
doesn't address the complexity of the migration issue, but it would certainly
make scripts more clear.
--
_____________
Brennan