RE: [Pyblosxom-devel] category listings

[will <wi...@bl...>]

There's already a max config parameter.  I'm wondering if we shouldn't 
have an override via the url.

I don't know how we want to handle ignoring certaing directories in
pyblosxom.  I would think this is the sort of thing we want to do globally
somehow.  Maybe tools.Walk should know about ignored directories and not
recurse through them?

/will


On Sat, 25 Jan 2003, Theodore W. Leung wrote:

> A max seems like a good idea -- the question is is it a form argument or a
> config parameter.
> Also, I hacked my local copy of pycategories.py to test whether there are
> CVS directories present.  I'm version controlling my data directory, so that
> I can check out a copy on my laptop and blog disconnected.
> 
> Ted
> 
> > -----Original Message-----
> > From: pyb...@li... 
> > [mailto:pyb...@li...] On Behalf Of will
> > Sent: Saturday, January 25, 2003 8:40 AM
> > To: pyb...@li...
> > Subject: [Pyblosxom-devel] category listings
> > 
> > 
> > 
> > I fixed up categories so it's all pretty now.  When doing 
> > that I noticed 
> > that if you browse by category, you only get the max number 
> > of entries as 
> > specified in the ini file.  I was wondering if it'd be a good 
> > thing to add 
> > a max override on the url like the flavour.  Something like this:
> > 
>    http://www.bluesock.org/~willg/cgi-bin/pyblosxom.cgi/dev?max=26
> 
> In this case, we would show 26 entries.  Would that be a good idea, or 
> not?  My concern is that old entries won't be viewable if we spill over 
> the max.  Of course, I guess it prevents people from pulling _all_ your 
> entries.  I don't know if that's good or bad, though.  How do other 
> *blosxom things handle this?
> 
> /will
> 
> 
> 

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