• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Gui Scripting V/S Automation tools
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gui Scripting V/S Automation tools


  • Subject: Re: Gui Scripting V/S Automation tools
  • From: Bill Cheeseman <email@hidden>
  • Date: Fri, 08 Jul 2005 16:17:53 -0400

on 2005-07-08 9:52 AM, Badrinath, Nandini at email@hidden wrote:

> - So when do you think people go in for buying automation tools and when do
> they choose to use GUI scrupting for automating their Mac application? Also
> how comfortable are people in using GUI scripting for their automation
> purposes.
> - Also wanted to know what is the future for GUI scripting? I am very
> interested in GUI SCripting.

There is no reason to think that GUI Scripting will go away. It is based on
Apple's accessibility API, which is more or less required by law under U.S.
disability legislation.

Not all applications are fully "accessible," however. In particular, several
of the most popular Mac applications that have been around for a long time
remain only partially accessible, at best, at this time. As a result, GUI
Scripting will not work with them as fully as it should. In addition, a
number of applications -- including several from Apple -- use custom code
for non-standard user interface elements, and even Apple hasn't made all of
these non-standard UI elements accessible. Hopefully, this situation will
improve over time, because it is very easy to make custom UI elements
accessible.

In general, GUI Scripting serves limited purposes, including these:

1. Automating the testing of an application's user interface.

2. Scripting aspects of a scriptable application that are not available
through the application's built-in scriptability.

3. Scripting non-scriptable applications.

If an application gives you a choice between performing a task using its
built-in AppleScript support and performing the same task using GUI
Scripting, it is almost always better to use the built-in scripting. It is
likely to be considerably faster, and it probably won't have to open menus
and windows as GUI Scripting sometimes requires.

--

Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com

PreFab Software - http://www.prefab.com/scripting.html
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes


 _______________________________________________
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

References: 
 >Gui Scripting V/S Automation tools (From: "Badrinath, Nandini" <email@hidden>)

  • Prev by Date: Re: AppleScript error, overflow.
  • Next by Date: Re: Facespan dead?
  • Previous by thread: Re: Gui Scripting V/S Automation tools
  • Next by thread: AppleScript error, overflow.
  • Index(es):
    • Date
    • Thread