|
The main changes are:
Changes 16/2/2002
A number of design changes were made to make the framework easier
to work with and tolay the foundation for forming an API.
Design of tiler and any geographical output classes now follows the
Composite design pattern. There is a new interface for GUI plugins,
and a new interface for scene generator plugins (a scene generator
is my term for whatever creates things additional to the
terrain. e.g. geometry in which the terrain resides,
viewpoints, tour interpolators, buildings, features etc).
Some
internal redesign, debugging etc.
Modifiable text is now managed
through properties files that sit in the appropriate plugins
directory, and there is a new interface for the modifiable text
handler, which, you guesed it!, can be another plugin.
Things to
watch out for:
- The RezTile interface has changed
- the parameters and config file fields have changed:
- the debug flag is set in the command line through a -D flag,
no longer as a standard Rez parameter.
- some redundant parameters are removed
- the config files are changed to allow gui, scene plugins and
to remove the separate tree builder plugin (the treebuilder
interface is still implementable but its instance must be called
from the buildTree method of the RezTile instance.
- tiles and images no longer have an alphabetic character
(corresponding to level) appended to the file name
I think with these changes the Rez system becomes a true
(embryonic) framework and it sets the stage for easier expansion of
its uses and capabilities.
New sample plugins:
- A sample plugin GUI (in rez.plugins.gui)
- A scene generator plugin for VRML models (in
rez.plugins.scene)
There is now only one plugin interface for multiresolution
tiles (if a separate tree node generator is required it is called
from the tiler).
I plan to do a bit
on Java3d next,
cheers,
chris | 
