Re: iWork Pages
Re: iWork Pages
- Subject: Re: iWork Pages
- From: "John C. Welch" <email@hidden>
- Date: Wed, 26 Jan 2005 09:27:52 -0600
On 1/25/05 8:22 PM, "Michelle Steiner" <email@hidden> wrote:
>> That's a bit strong. But it's safe to say that AppleScript is not
>> held in high esteem in every group at Apple. Then that is apparent
>> from the products, isn't it. If there were a mandate from Steve Jobs,
>> it would change that situation, but I wouldn't hold my breath waiting
>> for that.
>
> It could be that they felt that implementing Applescript in Pages would
> be wasted effort with Automator coming soon in Tiger. I would not be
> surprised if Automator workflows were already embedded in Pages.
>From the public API for automator, there's only two ways to do Automator
modules for an app.
1) the application puts in a decent dictionary, and the modules are then
written in studio. This is the easiest way to support Automator, and gives
you the widest potential range of Automator module creators.
2) You use Cocoa frameworks for everything, expose and document all your
uses of said frameworks, and force all the modules to be Cocoa - only. This
of course, is much more complex for what Automator is designed to do, and it
severely limits the number of people who are able to write modules.
Note: if approach 1) is taken, you don't limit approach 2) for Cocoa
applications. However, if you refuse to implement AppleScript in your app,
then approach 2) is the only possible option.
--
"Any ship can be a minesweeper... once."
Anon.
_______________________________________________
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