Hi! This is Mooquackwooftweetmeow, a collection of stuff by Greg K Nicholson.
Last night version 1.0 of The Twaddle went live. It uses arbitrary XML and XSLT to generate valid XHTML pages... offline.
I did manage to get the XML+XSL-based jiggery-pokery for The Twaddle working - quite nicely, actually. Getting the entire contents of the content field onto the page took a little bit of effort, as described on the mozillaZine forums.
Evidently Opera doesn't like XSL - this weblog shows up as a lot of plain text with the odd URL chucked in. The question is whether I care.
As a prelude to some major back-end renovation I'm planning for The Twaddle, I decided to see if I could get Internet Explorer 6 to display this XSL-ified weblog nicely, not accounting for IE-unsupported CSS (which is already taken care of at The Twaddle). Previously, IE displayed the DOCTYPE declaration as plain text at the top of the page; using strategic HTML commenting, I've managed to prevent it from doing so.
That w3schools (http://www.w3schools.com/) is pretty decent. I've now concocted an XSL stylesheet for this feed, so visiting its URL in a (good) web browser should display it as a nice page.
Well, then... this is an atom weblog. Why's it only in atom format? Everything on Mooquackwooftweetmeow is done the old-fashioned way - using the human brain, a plain-text editor, and no PHP, ASP, SQL or any other fanciness. And I don't want to have to copy every entry out into an XHTML page. I'm thinking of having a bash at some XSLT, to automatically generate a fancy front for the weblog; I tried it with the RSS feed, but didn't quite manage it satisfactorily; perhaps my standards are just too high (after all, I am using a free web host).
Questions? Comments? Plaudits? Microblog at identi.ca/gregknicholson, or with the tag #xsl; or email me at greg@gkn.me.uk.