Will's blog

purpose: Will Kahn-Greene's blog of Miro, PyBlosxom, Python, GNU/Linux, random content, PyBlosxom, Miro, and other projects mixed in there ad hoc, half-baked, and with a twist of lemon

[ home | blog home | recent activity ]

Tue, 08 Mar 2005

PyBlosxom 1.2 plans

We're going to try to push out PyBlosxom 1.2 in the next week or two. Steven did a lot of work fixing up static rendering and also fixing the architecture pieces that caused PyBlosxom to kind of suck when used in various frameworks like WSGI, Twisted and mod_python. I'm also going to do another round of documentation content.

We're going to push fixing the file handling to the next version. We want to allow for index caching and also reduce the number of times PyBlosxom walks your blogdir for entries. Both of these new abilities will significantly reduce the time it takes for large blogs to render. Getting there....

The plan is to have these changes in before Ted's talk at PyCon.

[ tags: dev, pyblosxom, python | category: /dev/pyblosxom | Permalink | View/Add Comments: 3 ]

Comments:

Posted by Sridhar Ratna on Tue Mar 8 23:04:28 2005
Yes, directory walker can be made optimal.  To get recent entries, just walk from last_year/last_month/last_date ('yield' the entry).

Archive browsing should be like LJ and not like WordPress.  Only then, filesystem based blogs can be easily implemented.

Also please try Nevow for template system.  It is really cool, such that it totally separates content and presentation. I have made a working wsgi.py and cgi,mod_python examples here - http://srid.bsdnerds.org/hacking/wsgi/


Posted by Steven Armstrong on Fri Mar 11 21:57:21 2005
I've written a nevow renderer for pyblosxom.
Two problems with this. The flexible plugin architecture alows plugins to directly generate data/content. This makes it somewhat difficult to integrate with a system like nevow. How do you write generic data_ and render_ methods if you, from the renderer point of view, have no idea what kind of data plugins might have added?

The other problem, which is the primary reason I stopped investigating this track is performance. The current Pyblosxom rendering system is more then twice as fast as the nevow renderer.

btw: I hardly did any work on static rendering. Only fixed bugs which I had created myself :-))


Posted by will on Mon Mar 14 12:22:01 2005
I did a bad thing and took the conversation with Sridhar offline.  But, to sum up really briefly:

1. The nature of our filesystem prevents us from doing this since we don't store things based on a time-oriented directory structure but rather a category-oriented directory structure.

2. I think LJ and Wordpress are cool.

3. I don't think PyBlosxom should become another LJ or Wordpress.

4. I don't think that static archives are the only way to do archives for a file-system based blog (but we do need to fix PyBlosxom's file-system handling).

5. I think Nevow is cool.  Our rendering system is open in the sense that people can build whatever renderer they want.  You're not limited to the blosxom flavour template system.  (see Steven's coments for more on Nevow as a renderer for PyBlosxom).

Getting there....


Post a new comment:

Three things:

  1. New comments get placed in a "draft" status and will NOT show up on the site until I explicitly approve it. Sometimes that happens within 24 hours.
  2. I reserve the right to reject/remove inappropriate comments.
  3. Sometimes I'll reply to a comment directly in email--so make sure your email address is correct.

If you can't for some reason post a comment, send me an email: willg at bluesock dot org.

Your name:


Your e-mail address (this doesn't get displayed to anyone--sometimes I'll reply directly to you):


URL of your website (optional):


Comment:


Yes, I am a human!

pyblosxom::1.5-dev git-master

Copyright 1996 to 2012, Will Guaraldi Kahn-Greene, under the Creative Commons BY-SA 3.0 license

Creative Commons License
Will's Blog by William Kahn-Greene is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.