I'm curious - what things were not-so-nice to do in XSLT? I've been idly poking at my own outliner in PHP, but my stuff's mostly dealing with XHTML and converting to OPML at the end. But, I've been using XSLT for all the major XML-based operations so far. I tend to like that better than DOM fiddling, for the most part, but I haven't gotten that far into my project yet.
2007-01-02EST19:25:22+00:00
#
The OPML blog rendering part - where you take OPML and turn it in to HTML. I was doing it with XSLT, but I needed to do a lot of string manipulation - and that's a lot easier to do with PHP than XSLT.
Again, I could have probably done everything I'm doing with XSLT (with registerPhpFunctions or whatever it's called), but it's better not to because then people will take the XSLT and drop it in - then I'll have to support them. I'm also hoping that I can add a plugin architecture later in the project, and that'd be easier to do with PHP rather than XSLT.
2007-01-02EST19:47:21+00:00
#
Again, I could have probably done everything I'm doing with XSLT (with registerPhpFunctions or whatever it's called), but it's better not to because then people will take the XSLT and drop it in - then I'll have to support them. I'm also hoping that I can add a plugin architecture later in the project, and that'd be easier to do with PHP rather than XSLT.
Ahh, okay. I'm starting from XHTML and going to OPML, so that's probably easier. Seems less of an effort to escape generated markup in XSLT than to turn escaped markup in attributes back into markup proper. I've done it, though it's painful.
2007-01-02EST20:54:50+00:00
#
