Re: Libraries and effiency
Re: Libraries and effiency
> I think I can only agree with your school-marm-like finger wagging in the case of applications so yes, I should have been more specific.
I think OSAX should be included, and when I see those kinds of commands in the dictionary I react the same way as if a developer put the "File" menu where the "Help" menu should be. I also wonder if they can't get that right, what else have they gotten wrong?
Terminology conflicts are fairly rare and fairly easy for the "Osax" developer to avoid.
>
> Otherwise, my suggestions hold. For example can easily realize the lure of using the obvious "import" and "load library" in an OSAX only to discover that developer B has used the same terms in his.
>
> To this effect, I have filed a bug for osaxen to at least have the ability to be addressed something like:
>
> tell osax id "ca.aker.osax.WCHandy"
>
> so as to eliminate the possibility of terminology conflicts.
At this point the "OSAX" become a FBA and should be developed and distributed as such, which is probably the best way to go for the library loaders.
ES
_______________________________________________
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