RE: [Pyblosxom-devel] Lucene and comments

[Theodore W. L. <tw...@sa...>]

Ok,

I've committed changes that make lucene work in a plugin style way.

I added a new kind of execute method to api.py, so that the executed
handlers can return a list (in the case of lucene, a list of files).  I =
then
added two new callback chains, one for CGI and another for the filelist.

When I added the callback chain for the filelist, I created a default =
plugin
that contains the code for the standard blosxom file traversal.  I'm not
sure that I like this approach because it puts the plugin directory back =
as
required.   Seems like it might be better to have pyblosxom.py contain =
the
code and somehow register it, but the plugin discovery mechanism (as it
stands) precludes that.

Please let me know your thoughts on this.

I totally don't mind comments that say "this sucks".  Part of the reason =
I
asked for feedback was that I didn't like it myself.  =20

I'll be looking at comments next, but I need to do a little Java hacking =
the
rest of today.

Ted

> -----Original Message-----
> From: pyb...@li...=20
> [mailto:pyb...@li...] On=20
> Behalf Of Wari Wahab
> Sent: Sunday, February 09, 2003 7:02 AM
> To: tw...@sa...
> Cc: pyb...@li...
> Subject: Re: [Pyblosxom-devel] Lucene and comments
>=20
>=20
> Theodore W. Leung wrote:
>=20
> >I'm back and caught up and ready to tackle a few things.
> >
> >#1.  I'm trying to figure out what is the best way to integrate my=20
> >Lucene code.For the file list, we need to turn the regular directory=20
> >walk into the default behavior (last in the chain) and let=20
> each plugin=20
> >before that return a list.  If any plugin in the  chain=20
> returns a list,=20
> >then handler processing is done.
> >
> This was discuss @=20
> http://sourceforge.net/mailarchive/forum.php?thread_id=3D1613664
> &forum_id=3D24361=20
> but still there is no real solution yet. If you've got some ideas, or=20
> working code, we could try test it out and see if we can use=20
> it for all=20
> situations.
>=20
> >#2.   For comments I have the following issues
> >We need a way to display a single article in a page, (so that we can=20
> >put the comment form up).  This probably just means invoking a=20
> >different template for the single article case.
> >
> Yup.
>=20
> >We (again) need a way to handle the comment CGI form post=20
> (probably via=20
> >the chain above).
> > =20
> >
> Again, the need for your point #1. :) To make life simpler, I'm=20
> suggesting a comment.cgi type of program to handle comments.=20
> We can make=20
> pyblosxom handle everything, but as feedback mechanism goes,=20
> you'll find=20
> trackback and pingback requiring xmlrpc mechanism to input=20
> feedback data.
>=20
> Then you'll need some management of feedback data, especially=20
> deleting=20
> feedback spam if necessary (of course to know if you're=20
> spammed, to need=20
> to mail every feedbacks to the users).
>=20
> I'm not sure what Blake have in mind, he would also like pyblosxom to=20
> handle POST and GET requests too. XMLRPC uses POST too, incompatible=20
> with GET requests and cgi module won't handle it.
>=20
> >We need a way to display the comment / trackback / pingback count=20
> >(retreived from the storage api) in story.html (via a=20
> variable) -- so=20
> >every iteration through valid_list needs to be able to talk to the=20
> >storage api.  This seems like another place for a callback chain.
> >
> Counts can be done by the standard load() plugins, iterating=20
> thru values=20
> of entryList at each call by using a standard incremental style of=20
> iteration. The plugin would call storageAPI to get relevant data of=20
> comment counts and what nots.
>=20
> >I just wanted to get your thoughts on this before I plunge ahead.
> > =20
> >
> More things to consider, how do you tell pyblosxom that you want to=20
> disable comments on a particular entry? Would some meta data=20
> like: #comments 0 in an entry work in order to disable=20
> comments? Also, what about making=20
> comments inactive for a particular entry as well? In my other blog I=20
> have to delete one entry because it recieved 100s of stupid=20
> comments and=20
> I can't disable it in MT (MT will fix that in 2.6)?
>=20
> Sorry if this mail sounds negative, I'mm all for feedbacks, I want it=20
> badly, but it does not seem to be an easy task with all these issue=20
> lying around.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something=20
> 2 See! http://www.vasoftware.com=20
> _______________________________________________
> Pyblosxom-devel mailing list Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>=20