sikuli-driver team mailing list archive

[RaiMan <question249084@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
This is currently by design ;-)

At startup of SikuliX (no matter if IDE or script run from command line)
tons of Java classes have to be loaded and pre-interpreted which adds up
to some seconds (with IDE this is split in 2 parts: IDE-startup and
first script run ), so it feels a bit smoother.

In IDE the second+ script run starts immediately, because we have a
running interpreter, that is just advised to run the script (which on
the other hand leads to some weird problems).

The problem is on the list with rather low priority.

What is missing is some background script runner.
The solution most often used, since it can also be used with remote machines is XML-RPC.
You have a running server, that is advised bay a client to do something. This works as fast as the 2nd+ run in the IDE.

Another funny option is to have the IDE run, while running a script,
that "sikuli's" the IDE, to run a script (one of some, that might be
preloaded).

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