Re: The future for AppleScript [was Re: where are the shell scripts ?]
Re: The future for AppleScript [was Re: where are the shell scripts ?]
- Subject: Re: The future for AppleScript [was Re: where are the shell scripts ?]
- From: Martin Orpen <email@hidden>
- Date: Fri, 11 Feb 2005 00:18:06 +0000
on 10/2/05 8:01 pm, Paul Berkowitz at email@hidden wrote:
> So the question is whether Cocoa Automator actions can actually be written
> for an app that does not expose its APIs. I don't understand how they could
> be. Even AppleScript Actions will be able to access system-level features
> via Cocoa commands, and enhance their capabilities that way as needed. But
> we're all talking here about application control.
My worry is that we will see an increasing number of apps which are provided
with a small number of Automator actions *instead* of AppleScript support.
Providing the Automator option gives a developer an opportunity to get their
app incorporated into a workflow solution without having to bother with
creating a nice AS dictionary.
I guess you could argue that it isn't too much of a problem as you can
inspect if the app is using public APIs to get its job done and then create
a script that does the same thing.
This seems too powerful to overlook because you can get so much useful data
with no effort at all.
For example, using Daniel's (http://www.red-sweater.com/AppleScriptKit.zip)
example application:
tell application "AppleScriptKit"
set foo to call method "standardUserDefaults" of class
"NSUserDefaults"
set bar to call method "dictionaryRepresentation" of foo
end tell
Gives you more environment information than you'd expect from a couple of
lines of script and an application that can be created in seconds.
--
Martin Orpen
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden