Re: flavours IV

On Sun, 20 Mar 2005, Russell Nelson wrote:
>
> Ahhhh, I see.  Maybe you could put that paragraph into 
> man_3_flavours.html ?  You start using the term 'flavours' without first 
> defining it.

I'm in the process of doing another version of the manual.  I'll keep this 
in mind when re-working the flavours chapter.  Thanks!


> > > 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.

You don't have to use an extension, though.

So the following are both valid ways to look at a specific entry:

    http://pyblosxom.sourceforge.net/blog/news/02232005.html
    http://pyblosxom.sourceforge.net/blog/news/02232005
    http://pyblosxom.sourceforge.net/blog/news/02232005?flav=html


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

I'm not sure what you mean by this.  Are you saying you think that the 
blosxom template system is too confusing for people to put flavours 
together with?  blosxom.com has 7 flavour packs not to mention the several 
that come with blosxom.

I'm not sure I agree with this statement.


> > > 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.

Well, I'll toss it on the list of things to fix.


> > 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.

That's interesting to know.

The official site (and I'm pretty sure there have been several 
announcements in regards to this) is now at 
http://pyblosxom.sourceforge.net/ .  That's where I've got the PyBlosxom 
manual which is coming along very very slowly but will encompass all 
aspects of PyBlosxom.

At the moment, I'm writing it myself while doing a bunch of other things, 
so it's just not getting much time in the queue.  Recently, I converted 
the whole thing to docbook and checked it into the repository.  So if 
anyone is interested in helping out, that's the place to look at.

I'll look into the default_flavour/defaultFlavour problem.

Thanks, Russell, for the insight.  I'll try to take what you've mentioned 
and fix some of the issues.

/will

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
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