Monday, May 20, 2002

My subscriptions list now has little miniature XML buttons and coffee mugs. To view the source for a channel, click the XML button. To subscribe to a channel, click the coffee mug. To view the channel's home page, click on its name. 21:39'14    comment []

The opml file I'm using to generate my blogroll now can contain macros which will get expanded at render time. The one I've added so far is a call to <%radio.html.drawNavigatorLinks ()%>, which makes my other navigation links appear to merge with the blogroll links. Also, after making a tiny change to my renderer, I'm able to point at the mySubscriptions.opml file in my gems folder, and generate the links to channels I'm subscribed to, which appear under my calendar at the right. It would be nice to have XML buttons and coffee mugs next to those links, but as a proof-of-concept, it works as-is. I wonder what other macros might make sense in my blogroll.opml... 16:28'11    comment []

MS Cites National Security to Justify Closed Source [via Slashdot] 15:25'27    comment []

Mark Woods: A Busy Writers Guide to Radio Renderers. 13:23'24    comment []

Jeremy Bowers: "Now... let's see Microsoft match that sort of performance." 12:59'28    comment []

Rick Klau suggested using a folder of OPML files to generate a blogroll. Each file would be rendered as a category of links. But I think it should be even easier than that. OPML already has the notion of hierarchy, so there's no need to push the hierarchy out into the filesystem. Each category would be a top-level heading (a summit), and its links would be subordinate headings. Of course, there's no reason that you couldn't use multiple OPML files -- if a summit is a link to another OPML file, then the contents of the linked file would constitute the category's links. 11:51'10    comment []

Thanks for the ETag explanation, Simon. 11:24'59    comment []