Re: tbpy plugin idea

Lance Weber <lance-kMc2rFPYsS/[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
Thanks for the heads up Wari and Ted, I'm going to poke around in the 
comments plugin before I do anything rash like reinventing the wheel - 
just as soon as I kick out all the vendors who've been besieging  my 
office this week. The critical point for me will be if the functionality 
can be enabled without turning comments on...

>>Sorry to reply this late that you have to resend :)

It's not you or any of the other good folks here at all. Sourceforge is taking 5-12 hours to publish my email to the list and I resent my first email because I thought the problem was on my end...

--L

Wari Wahab wrote:

>Hi there, Lance.
>
>On Tue, 2004-02-10 at 04:18, Lance Weber wrote:
>  
>
>>I've gotten basic trackback functionality working on my blog via tbpy.
>>http://www.alfheimstudios.com/blog/blogspace/trackback.html
>>    
>>
>
>Nice, I've always wanted to do something with tbpy in the past
>
>  
>
>>As I state in the above post, I'd really like tighter integration 
>>between pyblosxom and tbpy, especially for accessing and managing the tb 
>>entries, so here's some ideas for a tbpyb plugin:
>>   * Returns a count of trackbacks for the current entry
>>   * Exposes the rss trackbacks for the current entry as xml and html
>>   * Stores config variables for tbpy settings like url, data dir for 
>>embedding the RDF entries in your flav templates and accessing the rss 
>>tbpy files.
>>
>>I have a couple of questions for the group before I charge down this path:
>>1) Has this already been done? Is this a desirable featureset to the 
>>group at large?
>>    
>>
>
>Yes and no, no as in we have not done anything on tbpy. Yes as in the
>functionality is somewhat mirrored in the comments plugin suite that is
>included with the pyblosxom distribution. Ted Leung started this by
>looking at tbpy first, though not copying the code at all (Ted, am I
>right?). I do rather call the comments plugin a feedback plugin instead
>because it handles more than comments. Here's a list of features:
>
> * Integrated with pyblosxom
> * Designed with pyblosxom in mind
> * Keeps entries as RSS item in a seperate file
> * Trackbacks
> * Pingbacks
> * CommentAPI
> * Standard form comments
> * And as a feature: Not easy to install ;)
>
>  
>
>>2) The complexity appears to be low enough for "My First Python 
>>Project", as I'm just going to be reading some rss/xml files in the tbpy 
>>data directory and generating html from them. True?
>>    
>>
>
>Yeah, almost true. Complexity really depends on how you read the xml
>data, deriving useful information from it. I believe that reading XML
>data as is can be slow, especially when doing simple things like
>counting the number of comments in an entry. Which is why the comment
>plugin stores every comment in a different file based on timestamps.
>Easier to count that way, and need not worry about metadata in the RSS
>that tbpy produces.
>
>  
>
>>3) Am I missing some critical design/architecture flaw in this premise?
>>    
>>
>
>Not that I know of.
>
>  
>
>>Any feedback appreciated! --L
>>    
>>
>
>Sorry to reply this late that you have to resend :)
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>pyblosxom-users mailing list
>pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>  
>




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.