|
From: Theodore W. L. <tw...@sa...> - 2003-02-09 08:51:51
|
Hi guys, 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 = Lucene code. It requires a change in pyblosxom.py to process the form that contains = the lucene search term. It also changes the paradigm in pyblosxom for getting the list of files = to turn into the blog because the list of files now becomes the list of = files that come back from lucene. So I think that we need pair of callback chains: 1 to handle the CGI = form argument and 1 to handle the generation of the file list. For the = CGIForm chain, I think that if a handler in the chain processes the form, that handler processing is done. For the file list, we need to turn the = regular directory walk into the default behavior (last in the chain) and let = each plugin before that return a list. If any plugin in the chain returns a list, then handler processing is done. #2. For comments I have the following issues We need a way to display a single article in a page, (so that we can put = the comment form up). This probably just means invoking a different = template for the single article case. We (again) need a way to handle the comment CGI form post (probably via = the chain above). We need a way to display the comment / trackback / pingback count = (retreived from the storage api) in story.html (via a variable) -- so every = iteration through valid_list needs to be able to talk to the storage api. This = seems like another place for a callback chain. I just wanted to get your thoughts on this before I plunge ahead. Ted |