Related Entries

Do not use GET for form processing!
Google Visualizations quick start
SCM backed blogging - part II
SCM backed Blogging
Got linked in!

« Eclipse tutorials
» I.N.T.J

Trying out Blosxom

Blosxom is simply superb. Simple idea, big returns.

I downloaded Blosxom today. There are quite a few things I like about Blosxom already. Blosxom 2.0 is in beta now and supports plugins. I think I’ll wait for 2.0 and use it for blogging at work - especially as a uber bookmarker tool for bookmarking links I find interesting.

I love:

  1. Multiple levels of categories!
  2. Static rendering.
  3. Easy code*.
  4. Plugins.
  5. Flavours.

* - Somewhat easy! Not as easy to read as PyBlosxom.

What I might miss:

  1. Summary text for entries. I guess I can use a convention of second paragraph to be the summary and hack the code to understand it.
  2. Whenever I edit an entry, it is going to come up as a new entry. A simple touch can fix that.

  1. >> Whenever I edit an entry, it is going to come up as a new entry.

    That is exactly the feature I wanted in a weblogging tool for work. When a project is updated, I just update the entry, and the latest 'news' about that project automatically floats on top. Anyway, there's a utility that I have called editfile.py that puts back the timestamp for you so you don't have to :) Blosxom does have this nifty plugin called entries_index or something like that, it keeps a database of timestamps for all your files.

    For problem no 1. if you're using pyblosxom (which I don't think so), it's easy to create your own plugin that overrides the behaviour of reading '.txt' files. See:
    http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pyblosxom/pyblosxom/contrib/plugins/preformatters/moinmoin.py for an example code.

    Posted by: wari on April 29, 2003 10:57 AM
//-->