sikuli-driver team mailing list archive

[RaiMan <question173996@xxxxxxxxxxxxxxxxxxxxx>]

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

RaiMan posted a new comment:
--- build-procedure
agreed, that is not something you should do normally. You only have to do that, if you really want to add/improve/test something on the native C++ level.
Any other ideas you have may simply be added by using the standard Python/Jython or Java import features. Even the possibility to pack a complete Jython/Java solution into an extension is rather easy.

--- 1. installer - .skl
In my opinion, the .skl is something that should no longer be used by anyone using Sikuli X.
It does not add any advantages but only oddities.
The only thing of value might be, that you might send a .sikuli as one file over the net. But since a .skl is only a zipped version of the corresponding .sikuli, you might zip it yourself in these cases and unzip on the far end.
BTW: biggest disadvantage: .skl cannot be imported or added to the image path.
Recommendation: just forget .skl

--- 2. type()
known issue, see faq 933

--- 3. openApp() - use App class instead
but yes, on windows, it is a bit more complicated, since you have to distinguish between apps to be started and running apps (identified by their windows title).
Apps found on system path can be opened without using absolute path (which in fact is not the case for Firefox, Chrome and many other apps on Windows).

because I have to switch the machine, see next comment for an example.

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