RE: Porting to TurboGears

> > I am looking to write a blog under the TurboGears 
> > framework. One of my options is to port PyBlosxom
> > to TurboGears. I would first make it use Kid as the
> > template engine and then dive right in to using the 
> > framework.
>
> Well, I contend that at that point it's not really PyBlosxom.
> 
> However that brings to mind something I've been tossing around
> for a while.  I'm not sure what we should do with PyBlosxom after 
> 1.3 and the flavour overhaul.  I was tossing around reworking
> plugins, but I think I'm just going to retire and do minor bug
> fixes if needed, but otherwise it's done.  The reason being that
> PyBlosxom isn't really architected well enough to work with other
> frameworks and applications (MoinMoin, Trac, WSGI, ...) and since
> there are so many other blogging utilities out there many of which
> fulfill user needs far better than PyBlosxom does, there's not
> much point in continuing PyBlosxom.
> 
> Any thoughts on that?

I love the idea behind PyBlosxom, i.e. the file system determines
the blog layout, and many of the plugins have functionality that
is really useful.  Of course, I haven't needed it to do anything
more than it already does for a while now, so switching into bug-
fix mode wouldn't trouble me overly.

Of course, writing PyBlosxom-NG to fit into TurboGears/WSGI/Trac/etc
would be a fun project as well.  I hope you all would contribute
your collective experience to that project, if only in the form of
"We tried this, and it didn't work out so well" emails.

Later,
Blake.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click