When first working on the X3D code, we needed to produce a number of example
applications that would show X3D content and how the Xj3D library was used.
Swing was the user interface for this. One of the standard systems that we dealt
with was a JTree as that heirarchical structure nicely reflects the DOM
structure. So, as we thought it would be useful to users of the codebase all
over, we decided to expend a little extra effort in building a complete JTree
implementation that would interact with the DOM.
As the code was going to be publically used we wanted to make sure that it
functioned nicely. A simple hack was not going to be appropriate. The code had
to support the full capabilities of our implementation of the DOM. To do this,
we provided both static and dynamic aspects of the DOM specifications. Also, as
the user might only want parts of it, we decided to provide a full range of
options for swing pieces to be used.
Extending the Code
The current code has no knowledge of X3D specific items. That is, the items in
the tree could come from any form of document.
Anyone interested in this? I think it could help in projects using XML and Java.
Thank You and Best Regards, Joe
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:58:03 PDT