Re: Calling an application
Re: Calling an application
- Subject: Re: Calling an application
- From: Emmanuel <email@hidden>
- Date: Mon, 12 Feb 2001 20:49:13 +0100
At 16:25 +0100 12/02/01, Andrew Wylie wrote:
>
What advice might that be? I have a explanation from Marc and an ambiguous
>
hint from Emmanuel, the former is interesting and the latter perplexing,
>
neither seem heed able. I'm sure you know plenty from your experience but
>
you've demonstrated you don't know everything "what doesn't".
I have to admit that my post was neither rigorous, nor checkable.
It is perfectly understandable that such vague recommandations be not
granted for sure.
I am posting to make the following point clear:
Thorough testing of the various propositions is virtually impossible.
For instance, think that, you cannot make a test rigorous if you do not *at
least* re-install the OS from scratch frequently enough. The Finder's
database, the Alias Manager, AppleScript itself, store things, and you
cannot access those.
For another example, think how many simulations you've got to perform
before you can state "this script will work whatever the way the user will
update the software" (I mean, update the software which is being "told").
Copy the new version, then trash the old one. Replace the old one with the
new one. Install the new one, then copy also the old one to the disk. See
the new version only once through AppleTalk. Meet a more recent, yet older,
version on a Zip.
Letting alone OS updates, the script having itself a possible story (copy
it before / after it has already run ...) and many other things.
So, there are so many combinations that I feel obliged to be very prudent
when I assert generalities. On the other hand, I do my possible to remain
informed of the experience of as many users as possible.
And, finally, the one positive thing I know for sure on this topic is: the
raw code method has never failed.
Emmanuel