Xpresser

Differences between revisions 7 and 9 (spanning 2 versions)
Revision 7 as of 2010-11-08 14:42:01
Size: 4331
Editor: 189-73-144-110
Comment:
Revision 9 as of 2012-05-15 15:15:56
Size: 4582
Editor: eth3
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
  * python-pyatspi
  * python-gtk2
  * python-pyatspi2
  * python-cairo

  * python-gi-cairo
Line 16: Line 17:
Xpresser was developed and tested in Ubuntu Lucid (released in April of 2010), so versions of these dependencies known to work are the ones present in this distribution release. Xpresser was developed in Ubuntu Lucid (released in April of 2010), but is currently fully updated and available for the most recent Ubuntu releases. The project has an active team providing new features and updates on a regular basis.
Line 18: Line 19:
Please note that, even though Xpresser uses gtk to ''implement'' its features, at this point there’s absolutely nothing specific to gtk on the features and interface that Xpresser offers.
Line 22: Line 22:
Xpresser is copyrighted by Canonical Ltd., and licensed under the [[http://www.gnu.org/licenses/lgpl.html|GNU LGPL]]. Xpresser is licensed under the [[http://www.gnu.org/licenses/lgpl.html|GNU LGPL]], but we are in the process of converting its licence to GPL3.
Line 24: Line 24:
== Downloading ==
Line 26: Line 25:
At the moment, Xpresser is available solely as a Bazaar branch in Launchpad. == Getting started ==
Line 28: Line 27:
Execute the following command to download it: === Downloading ===
Line 30: Line 29:
  * bzr branch lp:xpresser Both source and binary downloads are available through the project's PPA on Launchpad: https://launchpad.net/xpresser
Line 32: Line 31:
More details about the project may be obtained in the Launchpad page:

  * https://launchpad.net/xpresser

== Documentation ==

=== Getting started ===
=== Fire it up ===
Line 112: Line 105:

== Get Involved ==
=== Hit List ===
 1. '''Documentation''': Updating our wiki with new features and commands.
 1. '''Unit Tests''': We need unit [[https://code.launchpad.net/xpresser|tests]] for the existing features.
 1. '''New Features''': Check out our existing [[https://blueprints.launchpad.net/xpresser|Blueprints]] or create some yourself...then code!
 1. '''Test and Fix''': No project is perfect, log some [[https://bugs.launchpad.net/xpresser|bugs]], or fix some.

What is Xpresser?

Xpresser is a Python module which enables trivial automation of Graphic User Interfaces (GUIs) via image matching algorithms.

Requirements

Xpresser depends on the following libraries to do its work:

  • python-opencv
  • python-numpy
  • python-pyatspi2
  • python-cairo
  • python-gi-cairo

Xpresser was developed in Ubuntu Lucid (released in April of 2010), but is currently fully updated and available for the most recent Ubuntu releases. The project has an active team providing new features and updates on a regular basis.

Xpresser is licensed under the GNU LGPL, but we are in the process of converting its licence to GPL3.

Getting started

Downloading

Both source and binary downloads are available through the project's PPA on Launchpad: https://launchpad.net/xpresser

Fire it up

Starting to use Xpresser is quite easy. All it needs to operate is a directory containing screen excerpts (images containing relevant crops taken out of one or more screenshots). These might be buttons, edit areas, image buttons, or anything else which could be relevant to perform an action on, or maybe simply to wait for its presence.

With this in place, an instance of the Xpresser class can be created:

>>> xp = Xpresser()
>>> xp.load_images("/path/to/images")

Clicking somewhere

If you want to press a button in the screen, for instance, you can take a screenshot of the button itself and maybe a bit of margin around it, and put the screenshot excerpt in a directory.

Then, assuming you've named the image my-button.png, you might simply do something like this:

>>> xp.click("my-button")

If you want to right-click instead, use the respective method:

>>> xp.right_click("my-button")

Besides using an image name as the argument, you can also use an image match instance as returned by find(), or an (x, y) pair.

Hovering over something

Instead of clicking, sometimes you may simply want to put the mouse cursor over something so that the interface reacts to this event. This can be done in a similar way to clicking.

Again, assuming you've named the image my-button.png, you might to do this:

>>> xp.hover("my-button")

Besides using an image name as the argument, you can also use an image match instance as returned by find(), or an (x, y) pair.

Waiting for things to show up

You may not want to do any action on the image itself, but simply to wait until something is shown in the screen before doing an additional action. This can easily be done as such:

>>> xp.wait("connection-established-indicator")

Besides using an image name as the argument, you can also use an image match instance as returned by find(), or an (x, y) pair.

Emulating the keyboard

If you want to use the keyboard to type some value in an edit box, for example, you can use the following method:

>>> xp.click("name")
>>> xp.type("John Doe")

Customizing the behavior on specific images

Sometimes, you may want to match an image even though it's slightly less similar to the original image you have taken the screenshot from, or you may want to click on a spot which is not quite the middle of the image you're matching.

Xpresser offers a convenient way to achieve these goals: just drop a file named xpresser.ini inside the images directory, and include sections in it resembling the following one:

[image edit]
filename = edit-text-box.png
similarity = 0.8
focus_delta = +50 +0

Each of these sections will customize the behavior for one image. The example above, for instance, will determine that the "edit" image will match even if it's only 80% similar to the original image, and if some action is performed on it (e.g. click), it will actually happen 50 pixels to the right side of the middle of the image matched.

Get Involved

Hit List

  1. Documentation: Updating our wiki with new features and commands.

  2. Unit Tests: We need unit tests for the existing features.

  3. New Features: Check out our existing Blueprints or create some yourself...then code!

  4. Test and Fix: No project is perfect, log some bugs, or fix some.

Xpresser (last edited 2012-12-22 22:48:08 by c-24-147-75-163)