<div class="gmail_quote">2009/7/16 Stefan Behnel <span dir="ltr"><<a href="mailto:stefan_ml@behnel.de">stefan_ml@behnel.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(skipping over your mail somewhat).</blockquote><div><br>Oh, thank you for that! =D<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Emanuele D'Arrigo wrote:<br><div class="im">
> I wish I could leave that to something indeed rather than having to<br>
> implement it myself. Unfortunately, although my original post referred to<br>
> xhtml, in practice I'm not dealing with a browser nor with xhtml. Instead<br>
> I'm attempting to write a GUI system based on Mozilla's XUL.<br>
<br>
</div>How does that discourage CSS?</blockquote><div><br>It isn't XUL or me working on a GUI system that does. But lxml does not have an etree.CSS() function which generates a CSS transformation, does it? However, it does have an etree.XSLT() function which generates an xslt transformation. Isn't it?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I didn't say "generate" them - just write them down. There's also a package<br>
called "cssutils" which you might (or might not) find useful for your needs.<br>
<br>
<a href="http://cthedot.de/cssutils/" target="_blank">http://cthedot.de/cssutils/</a></blockquote><div><br>Thank you for this! I did have a look and it has all sorts of nice things. Still, it doesn't seem to have functionality ordering the CSS rules according to the cascade nor there is functionality to apply all those rules at once to an xml/xhtml object. Does it?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It's common to use both: XSLT for structural tree transformations, and CSS<br>
for applying style information. That keeps the details of content structure<br>
and visual representation somewhat separated, which tends to be a rather<br>
big advantage.<font color="#888888"></font></blockquote><div><br>Totally agree. But in my case the content structure is already separate from the visual representation. It is stored in a XUL file with no style information. Only when I apply the xsl transformations XUL content gains style (and locale, in a separate xsl transformation) information.<br>
<br>I somehow suspect I wasn't particularly clear in my explanation of the problem. Was I?<br><br>Manu<br></div></div><br>