Re: [Pyblosxom-devel] pyblosxom 1.5 rc2 -- release soon?

[will kahn-g. <wi...@bl...>]

On 08/03/2010 02:43 PM, Sebastian Spaeth wrote:
> On 2010-07-29, will kahn-greene wrote:
>> The todo list for 1.5 is primarily composed of updating plugins, adding
>> tests, and fixing/updating documentation.
> 
> I feel very comfortable about releasing what we have now. If we can
> manage to make jinx or any other templating system work in 1.6, I'd be
> happy too. Right now it is .e.g. a pain to insert a html tag if a
> specific variable exists etc.

I haven't looked at your jinja2 renderer, yet.  I'm really really sorry
about that.  If we could get this working well in 1.6, that'd be really
great.

However, there are a few things we need to think about and figure out:

1. how does this affect plugins that have their own templates?  would
they require blosxom templates and also jinja templates?  how do they
know which set of templates to use?

2. would the new renderer expose a different set of rendering callbacks
or override the existing ones?

3. how much effort is it to package up a new renderer plugin like a
jinja plugin?  does it require additional packaging mojo that our
current plugin system doesn't do very well?


I'm interested in hearing thoughts on these as well as ways we can work
around the first and second issue.

Also, who else is interested in either a better rendering system or
switching to a new rendering system?  Is it possible to use the existing
blosxom on if we add an if block and comparators?

/will