Re: flavours IV

will guaraldi writes:
 > A flavour is a group of templates with a common "theme". ....

Ahhhh, I see.  Maybe you could put that paragraph into
man_3_flavours.html ?  You start using the term 'flavours' without
first defining it.

 > > Are there any other flavour files needed by other existing plugins?
 > 
 > It's impossible to quantify what existing plugins there are and what 
 > templates they might use.  However, you could look through the plugin 
 > registry and see what plugins are interesting and create the templates 
 > required by those.

Hehe.  You're making a distinction between what exists and what is
known.   If something exists and is not known, then I expect that
nobody cares about it.

 > > What problem does content_type solve?  Shouldn't it just default to
 > > text/html if it's missing?

You didn't answer my first question, but I inferred it from what you
said.  The answer is "Flavours can be used to return any kind of data,
not just HTML.  You could have a .jpg flavour, and it would return
image/jpeg".

 > > If I set defaultFlavour in config.py, it doesn't seem to affect the
 > > flavour of individual stories.
 > 
 > I'm not sure what you're getting at here.  Hopefully the confusion you 
 > might have is answered above.

It's answered in
http://pyblosxom.sourceforge.net/blog/static/man_3_flavours.html#3
(except that there aren't any name= anchors, but you know what I mean).

Basically, to generate html pages, your flavour files MUST end in
.html.  ?flav=whatever is useless for non-index files, as is
default_flavour, because the extension takes precedence.

Instead, what you need to do, when you want to play with page markup,
is to access blog.example.com/index.whatever, or
blog.example.com/ranting.whatever.

Once you're satisfied with that markup, you do this:
    rename .whatever .html *.whatever

I think the structure of the existing flavour system contributes to
the lack of published flavours.

 > > If I use ?flav=whatever, it is not passed into pycategories, so the
 > > flavour choice isn't propagated.
 > 
 > Ok.  That could be a bug in pycategories.  I can take a look at that when 
 > I have a free moment.  Alternatively, if someone else has time to look 
 > into it, that would be much appreciated.

Yes, it's a bug.  pycategories only knows how to fetch
category_flavour out of config.py.  It doesn't know anything about the
substitution variable 'flavour'.  I don't know how to access those
variables, otherwise I'd be sending a patch.

 > Hope that helps.  Out of curiosity, are you reading documentation we have? 
 > If so, which documentation have you read?

It's not clear where the documentation is.  If you Google for
pyblosxom, it sends you first here:
    http://roughingit.subtlehints.net/pyblosxom/
If you click on "documentation", it sends you to the Wiki.  That's
what I've been reading.  That has what appears to be documentation, so
I never found the sourceforge documentation you pointed me to above.

-- 
--My blog is at     blog.russnelson.com         | The laws of physics cannot
Crynwr sells support for free software  | PGPok | be legislated.  Neither can
521 Pleasant Valley Rd. | +1 315-323-1241 cell  | the laws of countries.
Potsdam, NY 13676-3213  | +1 212-202-2318 VOIP  | 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click