Hi Rod and All,
Sorry to take so long to respond.
The basis of the work is shown at:
http://www.web3d.org/x3d.html
Justin Couch is the main contributor on a lot
of the parser.
To me, the big deal is that we are using
Java/Java3D, but need the full W3C DOM,
with both static and dynamic aspects.
I still think XML and DOM are very basic to what
is required by OHS so I think this may be important
to whatever is being done. The 3D part of this work
will also be important when it is desired to provide
a user interface and mapping of content.
Thank You and Best Regards,
Joe
----- Original Message -----
From: "Rod Welch" <rodwelch@pacbell.net>
To: <ohs-dev@bootstrap.org>
Sent: March 16, 2001 9:37 PM
Subject: Re: New XML DOM and Java Tool
> Joe,
>
> Can you give a few brief examples of how this capability supports KM. Sounds
> like a lot of work has been done. Recently Eugene Kim provided a link to the
> web showing progress he is making. Is your work similarly on the web
> somewhere? Does it relate to Eric's specs for the OHS, or to Doug's letter on
> 001025?
>
> Thanks.
>
> Rod
>
>
> Joe D Willliams wrote:
> >
> > >From Web3D,
> >
> > Background
> > 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.
> >
> > Motivation
> > 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