fry
|
Processing 0136 makes new changes seem like old
May 29th, 2008, 4:45pm
ABOUT REV 0136 - 29 May 2008
This release represents the first of a set of major (internal) changes as we head to release 1.0 at the end of the Summer. This release will not be made the default download, but please test the release for problems on your platform, and file bugs (dev.processing.org/bugs) when you find them.
[ major changes, please read ]
+ New Runner The most significant change in this release is the introduction of a new runner system. This means that we'll be able to make the stop button behave properly, shut down sketches correctly, have better error handling, and eventually add debugger support. On the downside, sketches may start a little more slowly, and it may be a bumpy transition as we get things working (strange errors when you hit Run).
+ Switching to Java 1.5 We are moving to Java 1.5 as a minimum requirement for running Processing, as well as sketches created with it. This is an attempt at self-preservation as we try to limit the number of platforms that we support. Note, however that we *still do not* support Java 1.5 language extensions (enum, enhanced for loop, generics, etc.) More info about that can be found here: http://dev.processing.org/bugs/show_bug.cgi?id=598 If you find places in the code or reference that refer to Java 1.4 support, please let us know via dev.processing.org/bugs.
+ New XML Library We've switched to NanoXML instead of NanoXML-Lite. This means that the export size of the XML library has changed from ~6k to ~30k. The new version is much better at handling a broader range of XML content. The API should be the same and your code should work without changes (unless you're playing with namespaces, in which case those have to be specified differently). http://dev.processing.org/bugs/show_bug.cgi?id=757
+ Changes to how libraries are found Major bug fixing happened in handling the class path issues and dealing with how libraries are loaded. With any luck, this should fix the dreaded aiexport bug. It should also give better results when multiple libraries are installed on the system. However, it may mean that some libraries (or jarfiles) that shouldn't have been working before will now (properly) no longer work.
|