Re: "pybloxsom"??

On 02/23/2011 02:45 PM, seanh wrote:
> On Wed, Jan 26, 2011 at 05:39:15AM -0500, will kahn-greene wrote:
> 
>> I think if we decided to ditch the blosxom renderer for something sane,
>> then at that point, we'll have shed most of our blosxom roots.  At that
>> point it doesn't make sense to continue to emulate blosxom.  And at that
>> point, we could change the names and kick off a new project.  We could
>> probably spend some time fixing up other legacy problems that I created
>> like the total debacle that is entries.
> 
> The rendering engine is really what I don't like about pyblosxom.
> Whenever I try to do something with pyblosxom I end up fighting against
> it. It just wants me to have a blog where the front page shows the n
> most recent posts in full and then there are archive pages for each
> year/month/day showing all those posts in full. But that's just not the
> kind of blog format that I want. There are lots of different ways that
> people do their blog front pages and archive pages. So it needs more
> flexibility.
>
> [snip]
> 
> I guess this sort of thing can probably be written as a renderer plugin
> for pyblosxom?

I think that's a good start.  I suspect the big problem you're going to
run into is that the existing plugins expect the existing renderer and
might not work well with the new renderer.

Regardless, I think the only way we're going to figure that out and move
forward is if someone takes the plunge and starts identifying issues.

/will

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev