Slashdot Mirror
Mozilla + CSS + XML = Structured, Formatted Content
Saqib Ali writes "Publishing XML content on the web requires some heavy processing on the server. There are many publishing framework (AxKit, Cocoon, etc) available in the market. However they are very CPU intensive. Apple's Internet Developer has a article on how to use CSS along with your XML content to render the formatted content in the Mozilla Web browser. It is very interesting read, especially for people who want to start creating content in XML, but don't want to invest in a expensive processing server/application. They have a nice example of RSS feed (XML) formatted for publishing in the browser."
tu slashdot?
I'm as mimsy as the next borogove but your mome raths are completely outgrabe.
I'm working on a some web log analysis software to license under the GPL. The output will be XML that is linked to CSS and Javascript. Besides being easily parsed by another program, the output is pretty, and the tables can all be sorted by any of their columns. It uses DOM Level2 functions called from MergeSort implemented in Javascript. Watch my website, I should have it done, or at least a first version within a couple weeks.
Just when you think Phoenix has saved you thousands of precious CPU cycles over Mozilla, something like this pops up and fills the hole. Doh!
The link mentioned doesn't work well in Mozilla 1.2.1: no hyperlink.
;
And konqueror can't even render the page. It says its invalid:
XML parsing error
fatal parsing error: the document is not in the correct file format in line 6, column 37
<link>http://www.scottandrew.com</link>
^
DNA is the ultimate spaghetti code.
Having CSS functionality in XML is a Good Thing, but would it not be worth waiting for a full implementation of XSL functionality on the client side before embarking on a full-on application?
I thought the idea of XML was really to keep it server side...u know this whole platform independant thing they've been working to for ages? Dont wanna sound like a flamer but it seems pritty stupid to start the "oh you need this browser to view this site" wars again. Had enough of that in ye-olden days of NS vs. IE :)
"What do you mean you have no ice? Do you expect me to drink this coffee hot?" - Random Customer, Clerks
I feel your pain about getting XML/XSLT things working. Alas, until recently, Moz didn't handle basics like xsl:number properly, and the suggested workaround was "don't use it". Um... no. That made Moz pretty much useless for any serious XML/XSLT work I was doing. Apparently, that particular gremlin was a well-known one, and should be fixed in Moz 1.2, though, so maybe things are coming around slowly but surely...
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
Umm... yeah. Can show me how serialize C structs in *any* portable data format easily? Serialization in C is non-trivial. Serialization in a portable format is *incredibly* non-trivial.
It's always a long day... 86400 doesn't fit into a short.
Yeah, that's all well and good when you're writing managed code. Data structures in managed code have all sorts of nifty bits of meta-information floating about.
Now back to my point that serializing C structs is non-trivial.
It's always a long day... 86400 doesn't fit into a short.
One typical use of XSLT is as a translator between marked-up data (XML) exported from somewhere and a marked-up hypertext document (HTML) presenting that data or a subset of it for the web.
Neither the XML nor the HTML will necessarily contain any formatting information beyond HTML's fairly basic set of tags, so you might still need CSS to finesse the layout and appearance.
An alternative is to translate from XML via XSLT into XSL:FO, and from there into PDF (using Apache's FOP). This is a still-maturing technology, however, and it's a bit verbose for my liking - but you can say that about most of the X* family...
Experience is a hard school, but fools will learn no other.
Maybe gSOAP is the answer for your needs.
It is a library for C and C++ that generates codes for using (as a client) or providing (as a service) web services using the SOAP standard (based on XML).
If you give gSOAP a header file with the methods and structures of your code, it will generate all the needed methods and XML descriptors without giving you much trouble. From there it will be easy to serialize all your data in and out, and you won't have to care about the details of the XMLs. As an added benefit you will be able to share your data with software written in several other languages.
Fh