Admittedly the idea was the spawn of an especially tedious day-long tech briefing with 200 word powerpoint slides, but really -- it would ease the difference between a standard page, a fuck-work page, a work-paranoid page and a threadsuck page, neh?
My XSLT is pretty limited, but it does need to improve.
I'm looking at the PHP XSLT engine, and it shouldn't be too bad ... we could start out small, with just the posts in XML and transformed.
I think.
But the whole page should be possible.
I think.
Well, if I've time, that's something I can work on.
Though my eyes may bleed.
How does using XML change our compatibity with various browsers?
The XSLT can spit out exactly the same HTML as we're using now -- it'll just make switching "skins" easier.
I'm just wondering where this fits on the priorities list, since it will make some things easier but take time away from other things.
I'll be scanning in the pic of the Petrie Sprog and the Thank You card, today. To whom do I send the files for upload to the server so everyine can see them?
Allyson, you can post them on buffistapics. (Sign in as buffistas@hotmail.com/superfoamy)
Or you can send them to me and I'll put them next to the Jossnote.
Oh. About the XLST -- the advantage it has is that some of the people working on it would be an addition to the current coding team, and therefore not drawing on the same (limited) resources.
Also, I have to learn XSLT for work. I can either make up use case, or experiment with Phoenix.
So while it mightn't be as high priority as some of the other requests, there are other factors.