Re: Scripting Additions: Embracing the Horror of Unix
Re: Scripting Additions: Embracing the Horror of Unix
- Subject: Re: Scripting Additions: Embracing the Horror of Unix
- From: "Stockly, Ed" <email@hidden>
- Date: Tue, 29 Jan 2002 17:35:26 -0800
AppleScripters should be protected from the "Horror of Unix".
In the context of this discussion, what that means is that using whatever method OSAX writers choose (C++; shell scripting; Java), AppleScripters should continue to see the same basic Scripting interface we've seen since System 7 using the same language and the same philosophy behind the language structure.
That means the commands should NOT be only accessible as "do script" commands or even faux handlers like:
command(parameters)
Instead we should see plain old appleScript commands with few verbs and multiple nouns. And the entire concept of learning one Scripting language enables one to script every scriptable application and the system, should be maintained.
Jon mentioned Ed Lai's method of applying an aete dictionary to Unix shell commands and that certainly seems to be good place to start, but any commands limited to administrator or root access in Unix would become extremely problematic for AppleScripters trying to distribute to users in a number of different production environments where users may not have access that a script requires.
I'm just hoping that this entire discussion focuses on protecting the average AppleScripter from shell scripting (or Python or Pearl scripting) rather than inflicting them upon us.
ES
oh, the horror... the horror...