sikuli-driver team mailing list archive

[RaiMan <question234686@xxxxxxxxxxxxxxxxxxxxx>]

Question #234686 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/234686

RaiMan posted a new comment:
Since I do not think, that your question is solved, the following
comments:

--- Leo Editor
... is some kind of approach, that allows to "outline" a workflow (program flow) in a way, people are used to when working with larger structured documents: the details are hidden behind a top level structure, that only consists of headlines. In the case of Leo, the details are dynamically created Python script snippets. Leo itself is scriptable using Python, so you would be able to add any needed/wanted additional or modifying features.

--- following a list of images ...
... would be some kind of "robot", that tries to find his way through some kind of visual world looking for the next image match around it, moving to that point and then looking for the next image.
But talking in Sikuli, the robot would do a bit more: each image has some additional aspect: an action to be performed, if the robot "sees" the image.
example: the next image might be that of a door and the related actions might be one or more out of: open, close, knock, go through, wait until it opens, crash it to be open for ever, ....
This exactly is what you can do with Sikuli: wait for some image to appear and then click this or something else, to get things moving to the next visual state.
So in the end each Sikuli script is a workflow (or outline speaking in Leo, where the details are not hidden).

--- using Sikuli features with Leo ...
... will not work out of the box, since Sikuli scripts are written in Python language, but the interpreter used is Jython (a Java based implementation of a Python interpreter at language level 2.5). So you will have the same problems using Sikuli in this context, as when trying to use Sikuli with Python: it is not possible, to directly use the Sikuli features (tightly coupled via API calls).
Possible solutions are all loosely coupled based on some inter process communication (batch scripts, running scripts in subprocesses, using some kind of RPC, ...).

*** Conclusion: combining Sikuli with Leo does not make any sense, since
it moves the complexity to a higher level, than needed. Your ideas can
simply be implemented, by just using the Sikuli IDE. It is up to you, to
use some outline approach, when creating your scripts (which in fact
would be some top down approach).

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.