
Where am I with OPML renderer? ![]()
SquatCrunch has picked up on my new OPML Editor blog renderer. I'm not prepared to release it because it's currently not very good. It does the job, but it's ugly and really needs to be cleaned up.
The plan is that I'm going to basically build out all the functionality of my new blog. It now does almost everything that my current blog does, but I'm hoping to give it a new look before I switch the feed over. I'm going to then use it for a few weeks and fix up errors. Then I'm going to slowly prettify the code until it's in a releasable state.
Unfortunately, I don't think that I can budge on the requirement of XSLT - although I may be able to help those without XSLT support available process their XSLT. Doing it through the DOM or SimpleXML is dull work. I'm not sure what to do for the folks without XSLT support. I may be able to offer them the option of processing their XSLT on my server at a small annual cost. It may be simpler just to change ISP....