Re: Scripting in OSX: Classic osaxen for Classic apps?
Re: Scripting in OSX: Classic osaxen for Classic apps?
- Subject: Re: Scripting in OSX: Classic osaxen for Classic apps?
- From: JollyRoger <email@hidden>
- Date: Sat, 09 Jun 2001 23:43:37 -0500
On 6/9/2001 8:06 PM, "Ed Stockly" <email@hidden> wrote:
>
So, when migrating those Osax that involve user interaction I'm hoping that
>
Osax developers will keep the current flexibility that's built into the
>
system.
Tell blocks are not our enemies. ;-)
The shared namespace is both a flexibility and the cause of problems that
have plagued script writers for years. The shared namespace is what makes
terminology conflicts possible. John's commands is famous for this very
thing.
I agree that there are certain number of situations (not very many though)
where terminology should reside in the global namespace. But the fact is,
most scripting addition terminology is better off in a private namespace.
For example, I bet you that 90% of Akua Sweets would be better off in a
scriptable application.
You can hope all you want; but most of my scripting additions are going to
become scriptable applications.
JR