Ok. My scripting techniques are slowly getting better and I'm rethinking the way I do things.
Currently I have one big library that contains a hodge podge of miscellaneous handlers for doing everything, date stuff, file and folder stuff, sorting, accessing Safari pages, messaging, etc. When I need one or more of these routines, I load it via a load script command.
The downside of this is, when I only need a date handler or a message handler, I'm loading the whole library.
Would I be better off if the handlers were grouped in separate libraries (say all the date handlers in one library, all the file handlers in a library, etc.), and each was loaded as needed?
This means I would have to go through lots of scripts and change the single load to multiple loads, depending on the usage. Is the efficiency worth it? Is there even any gain in efficiency by doing loads of multiple smaller libraries over one big library?
Also, how do I handle (no pun intended) using handlers from one library in a second library?
I.e. Library A needs to call a routine that's in library B. Right now, they're both in the same library, but if I break libraries up by commonality this will no longer be true.
Is load script smart enough to only include one copy in a script if it's loaded from both the main script and from a loaded library? Can a library scrpit even load another library? If not, what's the best way to "share" libraries?
I've been going through some of the articles on MacScripter but haven't seen this addressed yet. Any thoughts?
TIA,
Jim Brandt
Free AppleScript Library "AS Hole"