Michal doesn't like Blosxom, which, as I said last last item, I've been playing with lately. The code is a bit obtuse in places, and some people would say that's just how Perl is. Michal might look at PyBlosxom (doesn't sound like he already has). From that first weblog entry, though, it looks like it's mostly a translation from Perl Blosxom, which would make it still some ugly in places. (The win32 conversion instructions indicate it's not using the path character function to abstract that away, but is that good or bad?) I thought there was also a PHP version of Blosxom, but I can't find it; if it does exist, I've looked at it even less than PyBlosxom, so I sure don't know if it's worth anything.
The real philosophy of Blosxom is that it leverages UNIX. (As Rael says, it's the weblog app for all the hidden gadgets in OS X.) I believe you can do that and still have clean code. Because Blosxom is free software, someone could clean it up. If I were going to use it more, I might; I know Michal won't since he certainly doesn't have the time! DJ Adams' calendar script sure seems a lot like it, and I must admit while hacking on that I felt a little uneasy about ending up with so many variables declared in the main scope, but it doesn't seem to bother most people.
Comments
comment
The main reason I code pyblosxom is so that I can steer away from typing html by leveraging MoinMoin’s markup as well as the ability to use BloggerAPI. Basically it’s for work, not much anything else, IMHO a work weblog should not be a distraction to write and HTML markup is a distraction. I looked at blosxom and can’t grok the code at all. I wrote it in python, and made it easy for people to create their own entry parsers, and there are a few different entry parsers out there on the net, created by people who do not want a heavyweight MoinMoin wiki parser (I hope to get some code from them).
Unfortunately, modelling pyblosxom with blosxom in mind makes my code kind of, err, not very pythonic :). Which is one of the reason I want to do a rewrite, to support different templating systems and other pluggable stuff.
There’s nothing wrong with running pyblosxom for Win32, only that it creates funny hyperlinks with a \ instead of the standard /. System wise, the path works alright.
The PHP version (phosxom) is located at http://zhware.net/phosxom/phosxom4.php.txt . It is more featureful than pyblosxom having it’s own trackback and comments system.
comment
There’s another PHP version of blogxom, surprisingly called PHPosxom, that you can find at:
http://celsius1414.com/phposxom/
Robert Daeley, developer of PHPosxom, has been improving it constantly.