Re: Library Modules and Library Loaders
Re: Library Modules and Library Loaders
- Subject: Re: Library Modules and Library Loaders
- From: Tetsuro KURITA <email@hidden>
- Date: Tue, 31 Aug 2010 22:42:03 +0900
> Simple way is override “load script” command
>
> load script “name/space”
> load script URL “http://some.url/script” load script file
>
> I'll check out overriding it in an osax, but I know I can already do what you need with a new command. Say 'import', would look something like:
>
> import "name/space" -- no slash start means it's in a module
> import "name/space" from user module
> import "name/space" in library "Logic Utilities" from local module
> import "http://some.where/some.scpt";
> import "/path/to/my.scptd" -- slash start means its a POSIX path
>
> set handler_names to import handler names from "http://some.where/some.scpt";
>
>
> This might be the better way because then there would be no confusion as to what is Apple supplied and what is not.
ModuleLoader has already provide a similar command called "load module".
But this command is just an extra of ModuleLoader, because simple osax command can't resolve dependencies.
There is a reason why both of ModuleLoader and AppleMods load modules through a script object. This mechanism causes complex syntax to load modules. But It may be impossible to develop simpler syntax than one of ModueLoader without AppleScript language supports.
=======================================================
Tetsuro KURITA
E-mail: email@hidden
http://homepage.mac.com/tkurita/scriptfactory/en/
=======================================================
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden