For apple instal Script Debugger mac os x#

, the debuggable version of AppleScript used by Late Night Software's Script DebuggerĪnd AppleScript Debugger come in both a Mac OS 9 form (extensions called JavaScript and Script Debugger Nub) and a Mac OS X form (component files called JavaScript and ScriptDebugger). JavaScript, by way of Late Night Software's JavaScript OSA , the scripting language of CE Software's QuicKeys , the internal scripting language of UserLand Frontier (It also may be because the OSA itself hasn't quite lived up to its original promise.) Here are a few that I know of: This may be because developers have not felt much need to supply them. In actual fact there have never been many other OSA languages. AppleScript is the only OSA language supplied by Apple, and in fact is designated the default scripting component, the one that is used when no particular scripting component is specified. One of Apple's purposes in designing the Open Scripting Architecture was to provide a place for other scripting languages that already existed, and for yet others that might exist in the futurehence the 'Open' in its name. Number, which refers to the version number of the installed component that implements it you can find out what this is by running the following one-word script in the Script Editor:Īt the time of this writing, the result is '1.10.3'.

For apple instal Script Debugger install#

One nice consequence of this architecture is that Apple can easily release upgrades to AppleScript, and the user can easily install them, with no effect on any other part of the system. On Mac OS X, the same function is performed by a file called ponent, which is in /System/Library/Components this type of file is called a component file. Its job was to install AppleScript as a component under the OSA as the computer started up. You may recall that under Mac OS 9 there was an extension called AppleScript (in the Extensions folder of the system Folder). Is installed as the computer starts up and simply left in place, so that it's always available. So an OSA-savvy program doesn't necessarily think in terms of any particular scripting language it asks the systemin particular, the Component ManagerĪre presently installed, and if it wants to use one, the Component Manager provides access to it.īecause components are installed dynamically, this installation must actually take place while the computer is running. One thing that's special about components is that they can be installed and uninstalled dynamically.

(Components were not invented specially for the OSA they existed already in connection with QuickTime.) Think of a component as a piece of self-contained functionality made available at system level so that any program can hook up to it and use it. Under the OSA, a scripting language is implemented by a something called a component But what part? There was no good place, so a new one was created: the resulting structure is the Open Scripting Architecture (OSA). AppleScript needed to be available everywhere, and thus would somehow have to be part of the system.

For apple instal Script Debugger code#

, but this would mean that the user would run AppleScript code entirely from within this one application, which was unacceptable. They could have made AppleScript the internal scripting language of a single application, like HyperCard's HyperTalk

One of the conundrums facing the founders of AppleScript at this time was the architectural question of where the language should live. But, much to the disappointment of users and developers, there wasn't time to create AppleScript before the release of System 7 in mid-1991, and the bulk of the work was postponed until 1992-1993. When System 7 was being created, along with Apple events and many other new technologies, it was already Apple's plan to create a language, AppleScript, that would give end users access to the power of Apple events.