Re: [Pyblosxom-devel] Egads! Bugs?

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

I've had lots of experience with SourceForge over the last 3 years and I
really hate their documentation manager and forums system.  Tracking bugs
and features sucks unless you have a really small amount of them.  Now
granted it's free so it's lame to complain much.

I once wasn't a fan of the wiki, but after playing with it this last 
weekend I agree with Wari that it's a decent system for our documentation.  
It just needs some more content.  :)

In terms of the url handler, I can jerry rig that pretty quickly (1 hour)
based on what Blake wrote for the /plugin-info thing if anyone is
interested.  Essentially it'd involve creating a url_handler callback
chain which gets called at the beginning with the url and environment
data.  Then the first registered function that can handle the url in the
chain handles it and the chain stops.

Blake mentioned in a previous email a bunch of issues with this namely
what happens when two things want to handle the same url.  I think to that
I would say we're designing a pretty small system here and while that's
something to think about for functional completeness, I don't think it's
an issue we really care about (I know I don't care :) ).  If a plugin
writer has this problem, then they can always register themselves with the
callback chain with a higher priority and thus pre-empt other handling
function.

I think when a function handles the url, it's building the whole page and 
that's the end of our run.  I can't think of a use case where we'd want 
two different functions to handle the url and do different things.

I vaguely remember there being other issues, but I can't remember what 
they were.

/will


On Wed, 5 Feb 2003, 'Wari Wahab' wrote:
> 
> BTW, I cc to pyblosxom-devel as this topic spawns of to something that
> devel list might me interested in.
> 
> * Blake Winton <bl...@ph...> [030204 22:57]:
> > So, have you gotten any bug reports recently?
> 
> Being a python software (unlike perl blosxom) I don't have that much
> users giving me bug reports, if they have, they included a patch for it
> (interesting indeed).
> 
> > Are you using any of the SourceForge features, other than the mailing
> > lists?  
> 
> Tried to but with miniscule user base, I don't see sf.net to be a main
> focal point of activity.
> 
> > I notice that they have a place for bug tracking and another for
> > documentation.  
> 
> The documentation thingy is not as good as a wiki I guess, that's why I
> have a wiki site for documentation. Anyone who feels that the docs is
> lacking can always contribute if they need to.
> 
> > If anyone is submitting bugs, I'd love to help track them down and
> > fix them.  (Of course, if no-one is submitting bugs, good job! ;)
> 
> Bugs, what bugs? pyblosxom is 1000% bug free :) NOT. hehe. There is one
> or two lying about.
> 
> 1. Entry files that starts with a digit will fail to get picked up by
>    pyblosxom when using a single entry link:
>    See:
>    http://roughingit.subtlehints.net/pyblosxom/2003/Jan/31#1044019277
>    http://roughingit.subtlehints.net/pyblosxom/development/1044019277.html
> 
>    The second url borks. This bug requires some modification (or even
>    refactoring) of libs.Pyblosxom.startup() or could even be done better
>    with a urlhandler() thingy, which is not available yet. Which is why
>    I didn't fix this before releasing 0.6
> 
> 2. Proper url handler to handle things queries like 2003/Jan/index.html
>    or /development/index.html
> 
> I think the main point of this is that handling or URLs must be fixed or
> pluggable so that we can do sane URL handlings or handle other stuff
> like comments or searches, etc..

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