JEX Files

Author: Joseph Cai
Email: jbcai@wisc.edu

You can run JEX through these executables. Each of the folders has a bat command which runs on Windows and a Mac command that runs on Macs. 
To run, double click on the .bat file. It will automatically launch JEX with the correct arguments. There are multiple versions of JEX here. 
OldJEX is from an older, more stable version of JEX. It's very close to what's on Jay Warrick's github. 
The rest are from newer versions of JEX, which I have made modifications to. 
"Development" includes virtual functions, which have not been thoroughly tested and is the development version. 
The other one is from the last version before virtual functions were introduced. 
You can check out the current code on my github: https://github.com/jcai0791/JEX.
Disclaimer: The newer versions have not been thoroughly tested, and may be unstable. Use at your own risk.

JEX for Windows is a .exe file made with exe4j that runs without the console. It is the easiest way to distribute JEX for windows.
However, since it is unsigned, it might cause some problems with antivirus software.

To make JEX print out to console, change "javaw" to "java" in the command.

Email me with any problems or bugs you encounter or any suggestions you have to improve JEX. If you need a custom function for your workflow, let me know.

Instructions from Jay:

To run on windows double click the JEX for Windows.bat file.

To run on mac double click the JEX for Mac.command file.

Keep the script file in the same folder as the JEX.jar file for it to work.

Double clicking the JEX.jar file will start the application but with insufficient memory to do significant image processing tasks. The default is typically ~256MB. The script files start JEX with 1024MB (i.e. 1GB). To increase or decrease the maximum java heap space, change the last line in the script file (i.e., "java -jar -Xmx1024m JEX.jar"). Change the "1024" to as much or as little memory as you see fit. A decent rule of thumb is to not go over half the size of your computer's RAM (e.g., if you want to allow JEX ~1.5GB of RAM, set the number to "1500", etc).

I chose to deploy the program this way so that the console is displayed while JEX is open. It allows users to see the console output of the program which can be very helpful for when it seems things are not working.