Jeffrey Rodriguez wrote: > I think that this idea has a lot of potential maybe using the TreeWalker > method and allowing a way to register a filter then the > serializer could be customized to output user selected nodes. > A user can select and serialize a view of the DOM this way.
What do you think would be best here? Perhaps people aren't using the traversal stuff is because it's too new and/or there isn't enough documentation. Anybody else have thoughts? Anybody want to write some usage examples and documentation? > Yes, we need to figure this out. I think the safest way would be > to move this package to the org.apache.xerces namespace > Andy, by the way this package is in the org.Apache.xml not the > org.xml ( Am i missing something here? ). Jeff, we're talking about the proposed API that Arkin submitted. The proposal is in the org.xml namespace. At least it is on my disk. > Arghh!! excuse me!! SVG getting serialized to a JPEG image is quite > an interesting idea!. What is next, smil files to native realaudio > files? Okay, I agree that the example was out of control. ;) > >Objects, though. Perhaps a better example would be an XML > >serializer that outputs to WBXML. > > > > Yes, this is a good idea and I would like so see it implemented. WBXML > (binary XML) has a lot of potential specially for embedded devices, cellular > phone applications, PDA, etc. The only downside with WBXML is that it can't be serialized without buffering. If you look at the spec for it, it's more like "compiling" an XML document to a binary form. Just look at the string table that they have at the *beginning* of the file. Oops! That requires that you know all of your string symbols used in the document. Works well in a closed system but I would like a binary format that can handle arbitrary files. I have some ideas about that but I won't go into them here... -- Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
