TreeProcessor is a complicated beast, so examining the classes does not
lend any clues to what is going on. However, the key to understanding
TreeProcessor is the treeprocessor-builtins.xml file.
We have an XML document with the following DTD:
!DOCTYPE tree-processor [
!ELEMENT tree-processor
Did you miss Sylvains (and my) answer to your earlier question about the
TreeProcessor? http://marc.theaimsgroup.com/?t=10664158681r=1w=2
AFAIK Sylvain has written nearly all of (or maybe all of) the
TreeProcessor, Ovidiu created flowscripts together with Christopher.
/Daniel
Berin
Berin Loritsch wrote:
TreeProcessor is a complicated beast, so examining the classes does
not lend any clues to what is going on. However, the key to
understanding TreeProcessor is the treeprocessor-builtins.xml file.
?? Haven't you seen my explanation to your previous request?
See
Daniel Fagerstrom wrote:
Did you miss Sylvains (and my) answer to your earlier question about the
TreeProcessor? http://marc.theaimsgroup.com/?t=10664158681r=1w=2
AFAIK Sylvain has written nearly all of (or maybe all of) the
TreeProcessor, Ovidiu created flowscripts together with
Berin Loritsch wrote:
Daniel Fagerstrom wrote:
Did you miss Sylvains (and my) answer to your earlier
question about
the TreeProcessor?
http://marc.theaimsgroup.com/?t=10664158681r=1w=2
AFAIK Sylvain has written nearly all of (or maybe all of) the
TreeProcessor, Ovidiu
Sylvain Wallez wrote:
Berin Loritsch wrote:
TreeProcessor is a complicated beast, so examining the classes does
not lend any clues to what is going on. However, the key to
understanding TreeProcessor is the treeprocessor-builtins.xml file.
?? Haven't you seen my explanation to your
