Question #232998 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/232998
RaiMan posted a new comment: at (a): yes at (b): yes, but the wording should be: To import any xxx.sikuli, that is not in the same folder as the importing script, the parent folder of xxx.sikuli must be in sys.path. (you should never try to import the contained .py directly (which in fact would be tricky),because then you do not get the automatic image path handling) at (c): It will contain some bug fixes (especially the observe feature is completely revised) and be more verbose for debugging problems. There will only be one sikuli-setup.jar for all systems, that you download. This has to be run and you select your Sikuli usage option, which in turn will download either sikuli-ide.jar (IDE) or sikuli-script.jar (Script) (does not contain the IDE). The needed native libraries are contained in the jar and exported at runtime to the parent folder of the jar. special for Windows: - the jar must be in a user writable folder (the ProgramFiles folders can no longer be used) - it takes care for the correct setting of the system path - on Windows 64-Bit you can use the same xxx.jar, to either run with a 32-Bit or 64-Bit Java (the libs are switched at runtime). Both (IDE and Script) accept the same command line parameters, but only IDE will allow to open xxx.sikuli for editing. The 2 command files sikuli-ide and sikuli-script (Windows: xxx.cmd) will no longer do any command line parameter handling (all done in IDE or Script), but only allow to select a specific Java version (e.g. to switch to a Java 6, if Java 7 is the default). For people who want to develop in Java and/or Jython using Eclipse or other IDE's, there is an additional new sikuli-java.jar, that contains the API support for Java and all supported scripting languages (currently only Jython, but JRuby and others to come with 1.1 later this year), but no interpreter (Script contains the full Jython 2.5.4). You have to use your own interpreter installation to run the scripts. The usage will be easier: - sikuli-java.jar has to be on the class path - the python path to the sikuli Lib folder will be added automatically at runtime - additionally it will be copied to the libs folder, to use it in IDE's to support the automatics of the editors (autocomlete, ...) So all resources needed will be automatically prepared at setup. Only in the main script you have to add one line import org.sikuli.basics.SikuliXforJython to tell Sikuli, that the Jython support is needed. So the process to prepare for Jython developement in Eclipse will be reduced to selecting the option at setup and adding the relevant paths to your project. Scripts developed using sikuli-java.jar can be run with Script or opened and run with IDE, if they conform with the xxx.sikuli structure convention (As already mentioned: to open and/or run plain .py files will come later this year). So for your plans: - just proceed as you started (this is supported even better in the future) - your users only need a Java on their machines and copy sikuli-ide.jar from somewhere in your companies network to a user writeable folder on their machine. Then they might just double click sikuli-ide.jar and have fun. Nothing else is needed any more. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
