I have whipped up a script that imports all the content from vital.org.nz into burble.

I wasn’t really planning on migrating that site over. Burble was meant to be a platform for some other things I’m cooking up, not a replacement for Blosxom. I just wanted to feel confident that burble would work well with a reasonable volume of entries and comments — and it does. Well enough that I’m wondering if maybe I shouldn’t go the whole hog and run everything on burble. That’d be kind of cool.

I’ve also fixed a little problem with Etags.

This is what my to-do list looks like for Burble:

Write query to retrieve posts by tag
refactor sql methods in model to do substitution and avoid SQL injection properly (see http://initd.org/pub/software/pysqlite/doc/usage-guide.html#executing-sql-statements )
Write template and handler for posts by tag
OpenQuestions
ComponentisedTemplates
Write query to retrieve posts by date
Write template and handler for posts by date
Refactor response so we can redirect

Write comment functionality:
    – get sessions working
    – design CommentProcessFlow
    – design CommentDataAttributes
    – write CommentAndCommentDAO
    – merge CommentController and SingleEntryController (GET and POST)
    – write CommentFormTemplate
    – investigate turning forms into Entries.
    – implement CommentProcessFlow
    – implement AntiSpam
    – retrieve comment count for entries
    – hyperlink comment author names
    – make anchors for comments
    – we shouldn’t allow comments on nonexistent ids
    – clean up session after comment post.

EtagManagementAsADecorator?
ArchiveCalendarWidget
TagCloudWidget
AdminAuthenticationDecorator
AdminConsole
BlogRollWidget
Tags should be able to have spaces
RecentCommentWidget
NonBlogPages
RSSFeed
implement TitleController
SetupOnTextdrive
Move methods out of model.EntryDAO into services
ImportOldContent from vital.org.nz
CachingStrategy

You can see there isn’t much left to do.