Quoth Michael Ross on Wednesday, 10 November 2010: > Am 10.11.2010, 01:09 Uhr, schrieb Robert Bonomi <bon...@mail.r-bonomi.com>: > > >With a GUI there is no way to describe the series of mouse > >'motions'/'clicks'/ > >'double-clicks'/'drags' and keypresses required to perform an operation. > >'screen coordinates' are meaningless when a window, or icon, or button, > >may be > >'repositioned' at will. > > > >An _individual_ application may allow scripting via an internal command > >language, > >but since it is internal to the app, and *not* part of the GUI, it > >doesn't > >'generalize' (no guarantee that similar capability is present in any > >other app) > >*AND* is utterly worthless for 'automating' annything that involves more > >than > >the single app. > > For Windows OSes there is actually a rather nice tool out there, > > http://www.autoitscript.com/autoit3/ > > which allows you to script the GUI cross-app. > > Regards, > > Michael > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Yes, there are a number of tools that allow one to script a GUI, many of which do not require knowledge of exactly where Gui element is located. However, for automating repeated tasks (as distinguished from running automated tests of the GUI itself), scripting a GUI is the wrong way to do it. It's layering on an entirely unnecessary layer of abstraction (the UI), and then working around it. -- Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com | http://chipsquips.com
pgpEDviPYbUlX.pgp
Description: PGP signature
