Calling script libraries
Calling script libraries
- Subject: Calling script libraries
- From: Malcolm Fitzgerald <email@hidden>
- Date: Thu, 18 Apr 2002 16:50:25 +1000
To some extent this is a RTFM question but I'd like to get some
opinions. I'd like to get some feed back on the best way to call
script libraries. I have several complex libraries that do specific
jobs ( FMP, WEB, Backups, etc). To date I've had a fairly small set
of "complex" libraries and I haven't paid much attention to modular
code. I'd simply do the job within the library. Now I'm cleaning up
my libraries and in the process I've created a set of libraries that
contains all the extra bits and pieces that I think are fundamental
(strings, lists, TID trickery, URLs/Paths, etc).
What's the best way of calling these library's into the work-space of
another library?
My woda_lib, for example, has five handlers that want to access the
basic libraries. Obviously it's easy enough to load the basic script
library within the handler but that seems counter-productive. Do I
want them to be global variables or properties and what's the best
method of accessing them from within handlers?
A side issue, this new level of responsibility is has been prompted
because I'm distributing my workload and the scripts will need to be
loaded onto half a dozen iMacs in our office. Its possible to point
to a central server and store script libraries there, alternately, I
can copy the script libraries to a standard location such as
"application support" on each machine. I'm plumping for the latter.
Are there pro's and con's to either approach?
--
Malcolm Fitzgerald
Database Manager
The Australian Society of Authors
phone: 02 9318 0877 fax: 02 9318 0530
http://www.asauthors.org mailto:email@hidden
_______________________________________________
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.