> (1) don't want to instantiate a DOM interface/object until I have too,
> because it is a memory hog
I think that is an understatement.
>
> (3) I like ECS, and and am used to it. Why should ECS be limited in
> that it cannot create a well-formed XML document with a prolog?
I like it as well, one of the primary reasons I wrote the core, and one of the
primary design considerations was extensibility you should be able to create
anytype of markup with it.
> (4) I like Jon ;-) and want to help make ECS even better
Guess everyone likes jon. =) ( at least everyone he hasn't told to rftm 100
times. )
> But I understand where you are coming from - however, I see ECS as a one
> stop shop for rendering *ML. I would like to add XML to that *, as well
> as HTML.
I disagree a little here, I see ECS as a one stop shop for rendering any type of
markup not just *ML. I'm currently working on a project that is built on ecs
that produces 100% valid rtf documents from fo trees. The cool thing about it
is we are using the 'EXACT' same style sheet to generate HTML and RTF using a
transformation engine i wrote that sits on top of ecs and uses reflection to
build the element trees.
-stephan
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
