Re: 'application' in OS X
Re: 'application' in OS X
- Subject: Re: 'application' in OS X
- From: Paul Berkowitz <email@hidden>
- Date: Mon, 19 Nov 2001 10:20:32 -0800
On 11/19/01 9:47 AM, "Emmanuel" <email@hidden> wrote:
>
At 7:34 +0100 19/11/01, Paul Berkowitz wrote:
>
>
>
> I have spent weeks on a set of scripts, only to come adrift today on the
>
> shoals of OS X's most peculiar and perilous handling of 'application'.
>
>
I would have thought that using pure text paths would eliminate any problem.
>
>
On Classic at least, you can use the full path name for a "tell application
>
theApp" as well as to "tell Finder to open theApp".
That's what doesn't work when switching from an OS X-native to a Classic
version of the same app (still booted in OS X).. (At least the full text
path is set to a variable.) Sorry if all my verbiage made that unclear.
From a later message of mine, also delayed about 8 hours so far, you'll see
that the problem disappeared when running the script from the OS X Script
menu. It's only an issue when running in Script Debugger in Debugger mode (I
think), although Mark believes it is an AppleScript issue at heart.
I haven't tried it yet in Smile 2.2 (serves me right!): it seems to be OK in
Script Editor, but I can't work properly there. In debugging mode in SD, at
least, the application is "retained" for the session and won't recognize
another application of the same name. I expect it would be the same in a
Smile Text window targeted to the OS X version of the app, which would make
it awkward to switch to the Classic version of the same app: I'd have to
switch text windows and targets, and would lose all my variable values. I'll
check later what happens when running as a complete script in a Smile script
window, but that's not quite how I wanted to work here: that would be
similar to working in SE.
>
>
Obviously AppleScript does very knowledgeable and useful things out of
>
aliases to apps, at the risk of making things unclear sometimes.
It seems more to be a feature of the brave new world of OS X with Classic
still around. In a year or so, I'll probably not be using Classic at all and
this sort of problem will disappear. I'm not sure that it's really worth
Apple's time to fix this sort of thing for what will be a just a passing
phase (co-ordination of Classic and OS X versions of the same app.) The
whole purpose of this script I'm working on is to use the Classic version of
Entourage as an intermediary for syncing Entourage X to Palm, which hasn't
released its OS X code yet. As soon as they do, and the Entourage developers
can come up with conduits, no one will need this script.
--
Paul Berkowitz