Moving toward Markup Object Events
Problem: Those damn attributes
In SAX, attributes are gone by the time you know what the element contains. Initially I handled this with a simple stack, but that wasn't enough to deal with recursive processing of element content turning into attributes. So...
Partial Solution: SAX and objects
I've started building container objects - mini-DOM trees, in a way - to temporarily hold information which arrives through SAX. I process the objects, and the objects send out SAX events when that processing is complete. I've made this facility into a more general toolkit, called Markup Object Events (MOE).
Next step: Rebuilding Regular Fragmentations on MOE
While I've just completed an alpha version of MOE, I still need to go back and integrate Regular Fragmentations with MOE. Having MOE available should substantially reduce the necessary code base, with only a bit of subclassing needed for the basic data structures. MOE accepts SAX events and generates SAX events, so this will still be a SAX filter.
Previous Page <
> Next Page