XML rendering

[Leo Savernik]

Am Freitag 04 Juni 2004 17:04 schrieb Zack Rusin:
> Ave,
>
> with the coming xpath and hopefully xslt, i've been looking into
> improving rendering of XML documents without stylesheets.
>
> Currently it's of course raw text nodes - which is also known in the
> rusin household as "this sucks" (i haven't patented this term, feel
> free to use it among yourself).
>
> I've been experimenting with different ways of fixing that (read as:
> making khtml crash more than test dummies on Volkswagen tests) and
> essentially we have the following options:
> 1) Create a bogus render tree.
[...]

Well, if you use xslt, you effectively get another dom representation. This 
representation will then be used for rendering.

Hmm, khtml could detect whether an xml document is served without a stylesheet 
(like Mozilla does already), and then set all the elements to display:none, 
and append an element containing a (e. g. tree-like) representation within 
the namespace html (which could be augmentend by JavaScript).

This is basically your number (2), but it doesn't introduce a permanent 
discrimination between a "DOM DOM" tree and a "render DOM" tree (which makes 
things more complicated and slower, given that this discrimination is rarely 
needed).

Though, to do that khtml needs yet to support JavaScript in xml documents.

Your idea to allow Render* to be augmented by plugins is a good one (I already 
thought about it in n7y). It makes perfectly sense to introduce an additional 
render interface on which plugins can be based upon (ksvg would massively 
profit from that). Though this has got nothing to do with "DOM DOM" and 
"render DOM" separation.

mfg
	Leo