------------------------------------------------------------ Release Notes for Transform SWF for Java, Version 2.0.4. ------------------------------------------------------------ This is a minor release fixing bugs and simplifying the package structure and build process. Bug Fixes FSCoord Transform now composites transforms correctly. Package Changes Examples are now included in the source tree. Simplified package structure and build targets. Datasheets are now generated using Javadoc. ------------- Bug Fixes ------------- 1. FSCoord Transform now composites transforms correctly. In previous releases values from the composited transform were being reused in the compositing operation rather than being saved to a temporary result matrix. Now fixed. ------------------- Package Changes ------------------- 1. Examples are now included in the source tree. The examples showing how to use the framework classes are now included in the source tree in the package com.flagstone.transform.examples. This is the first step in creating a unified package structure with all the source code in one location. 2. Simplified package structure and build targets. Classes are now compiled and packaged using a single ANT build file, build.xml. The previous version contained references to build files that were used internally to the projectand not normally part of the distribution. The build targets have also been simplified and made more flexible. A single target 'build' is not used to compile optimized versions of the framework and package the classes in a JAR file. For more detailed control, targets for each step in the build process are included, giving a choice to compile optimized or debug versions of the framework, compile the examples and to package all compiled classes in the JAR file. See the ANT file build.xml for more details. 3. Datasheets are now generated using Javadoc. Javadoc is now the preferred way of generating the class datasheets. Previously doxygen was used. While doxygen is an excellent tool the goal of simplifying the package structure made Javadoc easier to use and avoided the need to download and maintain another application.