PyBlosxom status: 11/13/2005

Note: This is an old post in a blog with a lot of posts. The world has changed, technologies have changed, and I've changed. It's likely this is out of date and not representative. Let me know if you think this is something that needs updating.

I re-re-wrote the flavour template code for the upcoming PyBlosxom 1.3 release. It works like this now:

  1. Pulls flavour templates from taste.flav that comes with PyBlosxom if that flavour exists.

  2. In either $datadir OR $flavourdir:

    1. If there is a directory named taste.flav, then it will take the template files from there and override the ones it got from step 1.

    2. OTHERWISE, it will look for files ending in .taste and override the ones it got from step 1.

  3. If the request is for a non-root path, it'll look in all the directories between $datadir (OR $flavourdir) and $datadir/path_info/ (OR $flavourdir/path_info/) looking for taste.flav directories OR files ending in .taste.

This allows you to put all your flavour files in a flavour directory that you specify in your file.

This allows you to put all the flavour files in a taste.flav directory (for example, html.flav, happygoodness.flav, rss20.flav, atom10.flav, ...).

This allows you to override individual template files from the default flavours. For example, if you wanted to add RSS enclosures, you can put a story.rss file in your $datadir/, $flavourdir/, $datadir/rss.flav/, or $flavourdir/rss.flav/ directory (depending on how you set things up) with the enclosure markup in it and PyBlosxom will pull the default rss templates and use your story.rss template.

This allows you to override individual template files depending on what category the user is looking at.

This makes it easier to package and distribute flavour packs because they can all sit in a single directory all by themselves.

There should be no backwards-compatibility issues with the new code between PyBlosxom 1.2 and 1.3.

NOTE: The code needs to bake a bit. I tested a lot of combinations of things, but I'm still finding occasional issues. This blog is using the latest code, so if you find any issues, write a comment below (assuming that's not broken) and I'll fix the issue.

I have one more big thing on my list of things to do for PyBlosxom 1.3. After that I'll probably release an RC1. Depending on school work, that could happen in the next few weeks. If you want to see the code now, get it from CVS (instructions for CVS access here).

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.