Re: AppleScript seems to be Unique...
Re: AppleScript seems to be Unique...
- Subject: Re: AppleScript seems to be Unique...
- From: "Jason W. Bruce" <email@hidden>
- Date: Wed, 01 Aug 2001 10:07:56 +0000
I think Windows provides similar functionality to AppleScript (really Open
Scripting Architecture) through what they call COM + (component object
model) automation. For the longest time, they had a feature known as DDE
(Dynamic Data Exchange) which was somewhat similar but was said to be
difficult to implement and not widely adopted. In recent years, COM was
upgraded to COM + automation, and appears to offer similar functionality to
OSA/AppleScript.
Jason Bruce
>
Message: 17
>
Date: Wed, 1 Aug 2001 12:26:56 +0200
>
From: Alexander Schrieken <email@hidden>
>
Subject: AppleScript seems to be Unique...
>
To: email@hidden
>
>
Hi all,
>
>
A couple of days ago I asked the list how unique
>
AppleScript was, and if Windows-users e.g. have
>
access to a similar utility.
>
>
The number of reactions to that question was
>
absolutely minimal (two). This could be
>
>
(A)
>
because there is no way Windows-users can do the
>
same things AppleScript let's Mac-users do, or
>
>
(B)
>
because the subscribers to this list are simply
>
unaware of the features that Windows offers in
>
this respect.
>
>
The first explanation seems most likely since the
>
only thing I could find that vaguely resembles
>
AppleScript is 'KiXtart' (<http://www.kixtart.org/
>
helpdesk/>, I was made aware of it's existence by
>
Monk). This program seems to be limited to
>
controlling the operating system however, and
>
would be comparable to AppleScript only if it was
>
limited to automating the Finder.
>
>
To our benefit AppleScript can also automate other
>
applications and even make them work together,
>
thus providing Mac-users with an unmatched
>
potential for system integration and workflow
>
automation.
>
>
The key to this feature seems to be the fact that
>
Apple provides a common scripting language for all
>
applications -- or at least the basis of it. I
>
suspect developers of Windows-applications don't
>
have this luxury, and must create some proprietory
>
macro-system if they want to offer the user the
>
ability to automate the program. Developers might
>
use the same macro-system in all of their
>
products, but that won't do much for integration
>
with other applications -- unless they're called
>
MicroSoft maybe.
>
>
Am I wrong?
>
>
>
Alexander
>
The Netherlands