The jar file is basically like an exe, except for java. On Windows you should be able to double click the .jar file and it will run. You can also use the java command from a command line.

Also here is the newest toolset and the most recent version (as in the one I am working on right now) of WZGUILIB.

Some changes:
Fixed a tabcontrol bug, fixed a bug in the Clicks function.
Changed what happens when you hit the titlebar of an unfocused form. Instead of it becoming focused and movable, it is now just focused and you have to click it again to make it moveable.
Added the page control. Similar to windows, and in fact inherits from window. It is basically like a window in the way it contains controls, but it is immobile and only one page can be displayed at a time.
I modified the way tabcontrols are drawn.

WZ should be a lot more stable too as I added lots of check code.

I added an error handler, and if you have a wzCons window it will print the error message to it.
I added code to the wzCons so that if the message is too large to fit into the window, it sets it to a new line.

I would expect another upload by tonight as I have a lot of development time.

This worked for me: java -jar "WZ_TAB_TOOL.jar"
You have to have quotation marks.

So, like I said here is another upload.
There is one major change. I used a modified version of the event distributer from inspired-lua and replaced all of the on events. Also, if you ever look back a couple of pages on this topic, you will notice an attached file that is called WZGUILIB_EV. The purpose of that file was to be able to take a WZ event, such as a window closing, and be able to run your own code in a callback function. This implements something similar, just with out all of the coding overhead. It is very simple,
form_or_dialog_name:bindEvent(string event, function callback). There is a catch though; at the end of your function before you return you must call the original handler code. This is possible because the first argument passed to your callback is the window that is supposed to receive the function. so if you had a form named winForm and a callback called closeCallback you can do this:
winform:bindEvent("close", closeCallback)

You closeCallback function then looks like this:
function closeCallback(window)
   print("Caught the close event")
   form.close(window)
end

This takes away a lot of coding and excess code from the original way that it was supposed to be done.

Does anyone know a good way to figure out an index of a string based on a pixel value?

That would be great. I am going to make several test applications in the near future, to release with WZ 2.5 in order to demonstrate several of the things that can be done with it.
Also I noticed that on Windows 8.1 the Nspire software dosent close properly, the window closes but it still runs in the background and wont let you open a new instance of it untill you kill the previous process.

Is there a way to get the value returned by a chunk loaded with loadstring?
I have tried:
pcall
xpcall
I also tried to set the environment with setfenv, but to no avail.

Can you post your code? So far I never have had a problem with it.