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: "Greg Strange" <email@hidden>
- Date: Tue, 26 Jun 2001 15:15:07 -0500
I just want to add my two cents in here if I may.
I don't know where I got the idea from but I always thought that having too
many scripting additions was a bad thing. My thoughts were that you have to
load the osax at startup and even if you never use an AppleScript (Dear God,
did I just say that?) your system heap and memory are taken up using the
osaxen. I of course am probably wrong.
I started everything on the Mac. I started using computers with a Mac, I
started writing on a Mac, I started fixing Macs, I started scripting Macs.
Then I moved into the dark world outside. I say that so that I can say
this: I have never figured otu why you can't load osax as you need them.
This would avoid Jon's Command coercing everyone's bellybutton and allow us
a little more contorl over our system heap. Why couldn't we just declare in
the beginning of the script the osax we need and move on? Something like
Perl's "use CGI;". This would add in streamlining development in my
opinion.
Having shown my feelings, I would say that I prefer to have osax become FBAs
wherever conceivably possible.
Just my two cents.
Greg Strange