|
/SW/website/blog/blosxom:
Moving from Blosxom to pyBlosxom
The most fundamental difference between the two is that Blosxom[1] is written in the Perl language, and pyBlosxom[2] is written in the Python language. Blosxom came first, then it was cloned to pyBlosxom, so the two are still exceedingly similar in look and feel and configuration.
I probably would have stuck with Blosxom out of inertia, but was unable to talk Blosxom into rendering Chinese characters, no matter what I tried. Chinese characters worked instantly with pyBlosxom[3].
Moving from Blosxom to pyBlosxom was quite easy, as layout is done almost exactly the same using a handful of "flavor" template files (head.html, foot.html, story.html, etc.) and my CSS layout worked right out of the box. I just had to adapt to the differences in plugins and other minor behavior.
I can immediately say that pyBlosxom does several things better, like moving configuration out of the cgi file and into a config.py file. The base url seems to be deployed more consistently, as my problems[4] with hard-coded menu links not working on my desktop have gone away. Website resources seem to be better organized, and generally the project seems to be more active then the Blosxom project
[1] http://blosxom.sourceforge.net/
[2] http://pyblosxom.sourceforge.net/
[3] http://blog.langex.net/index.cgi/China/links.html
[4] http://blog.langex.net/index.cgi/SW/blog/blosxom_desktop_and_server.html
posted at: 13:39 | path: /SW/website/blog/blosxom | permanent link to this entry