The IDE (meaning sikuli-ide.jar) is no longer intended to run scripts from command line. This is the job of sikuli-script.jar.
Nevertheless might it be of value in some situation to start the IDE with some command line parameters, that are available in the IDE, when running scripts as a global sys.argv.
This will be available plus the feature to edit these command line parameters prior to a script run in the IDE specific for each tab.
I plan to have something like the Maven pom's as configuration/preferences/setup/preset for the IDE and sikuli-script (XML or JSON format): if such a sikuli.config is in the same directory as the script or given by some commandline parameter, it will be used in this sense.
Thanks for the hint ;-)
The IDE (meaning sikuli-ide.jar) is no longer intended to run scripts from command line. This is the job of sikuli-script.jar.
Nevertheless might it be of value in some situation to start the IDE with some command line parameters, that are available in the IDE, when running scripts as a global sys.argv.
This will be available plus the feature to edit these command line parameters prior to a script run in the IDE specific for each tab.
I plan to have something like the Maven pom's as configuration/ preferences/ setup/preset for the IDE and sikuli-script (XML or JSON format): if such a sikuli.config is in the same directory as the script or given by some commandline parameter, it will be used in this sense.