sikuli-driver team mailing list archive

[RaiMan <question705963@xxxxxxxxxxxxxxxxxxxxx>]

Question #705963 on SikuliX changed:
https://answers.launchpad.net/sikuli/+question/705963

    Status: Open => Answered

RaiMan proposed the following answer:
Generally the type of an AUT does not matter when using features of
SikuliX, since it only works visually (on what the AUT displays on the
screen seen as rectangular pixel areas).

>>> try to record several actions on the GUI of the AUT ...
Currently SikuliX does not have a working recorder feature (but it is started again in 2.0.6).

>>> automate actions by executing (replaying) the scripts recorded previously ...
With SikuliX currently you have to write down your workflow yourself. The easiest way is with SikuliX IDE, that allows to run python-lang-scripts using the bundled Jython interpreter (version 2.7). With the IDE it is also possible to setup your images by capturing from screen, that are used in your workflow to recognise the state of your AUT (based on OpenCV) and then  do actions (mouse and keyboard) using JAVA AWT Robot.
Some basic app and window features and OCR based on Tesseract are also available

The SikuliX APIs are useable from Java programs (or Java aware
languages), in Jython/JRuby scripting and from C-Python scripting using
a java-bridge like pyjnius.

In any case the system running SikuliX based automations needs an
unlocked real screen and cannot be used in parallel by the user
(mouse/keyboard) without respective preparation in the workflow.

To get an impression it is recommended to read across the docs.

Tons of examples and user experiences are available in the net.

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for SikuliX.