Re: To OSAX or Not To OSAX?
Re: To OSAX or Not To OSAX?
- Subject: Re: To OSAX or Not To OSAX?
- From: "Steven D. Majewski" <email@hidden>
- Date: Sun, 22 Jun 2003 15:50:36 -0400
On Sunday, June 22, 2003, at 02:16 PM, julifos wrote:
I think that some required rules to share a project are speed,
reliability &
portability.
Of course, vanilla solutions are best than osaxen calls, but only if
the use
of vanilla doesn't slow down your script or make it unreliable.
As you say, I think the best solution for an user is a double-click use
(even better if he mustn't read documentation before use your app).
When you save an applescript as an application, does it include external
script libraries or OSAX ?
I had always assumed not, which is one reason I've avoided OSAX.
( Applescript Studio on OSX, using the new bundle format, however, does
provide a way to package up all sorts of resources into an applescript
app.)
How about other OSA languages and compiled scripts ?
Does compiling it mean you don't need the other language scripting
component to be installed on the target computer ?
( Here, I've been assuming that you DO need the scripting component
installed on the target. )
-- Steve Majewski
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.