Re: Thoughts on comments package

I don't think anyone I've seen on the list so far wants pyblosxom to 
turn into YAMP (Yet Another Monolithic Project) - heck, I was just 
ranting about java monoliths yesterday in my blog ;)

But, having said that, the question really comes down to how the end 
users view the tool. If you want your blog/pyblosxom to be the core 
engine of your site, then you're going to want tightly integrated full 
featured plugins like xmlrpc, the comments suite, etc. On the other 
hand, if you view your blog as just one component of your site that 
needs to interact with many other components (you could have a wiki, rss 
newsreader, blog, standalone trackback etc), then you may be looking at 
lighterweight plugins that glue external components to your blog, like a 
tbpy plugin to integrate trackbacks.

Of course, it's really up to the project developers to decide if they 
want to support full featured plugins as they require a much deeper 
exposure to the inner workings of the system. If you do, then you are 
going to have to live with people using the codebase in ways for which 
it was never intended and encountering all kinds of funky consequences.

On the other hand, making a conscious decision to only support a very 
narrow glue oriented API results in a much more manageable but limited 
code base, but at the cost of potentially shutting out those users 
looking for a fully featured core website application.

Frankly, if I had a vote I'd urge towards a minimal api that focuses on 
loosely coupled operations. But, I also just finished reading ESR's "The 
Art of Unix Programming" (highly recommended!) and I may have a 
lingering bias in that regards...


Wari Wahab wrote:

>On Fri, 2004-02-13 at 16:19, Ted Leung wrote:
>  
>
>>It seems like a waste for a trackback handler to run all the way 
>>through the pyblosxom pipeline in order to report a failure.
>>    
>>
>
>Yes, trackback handler is it's own CGI script, but I was talking about
>other plugins that can get the renderer from the args it receives as the
>renderer is in the request object.
>
>  
>
>>Actually, thanks for the reminder.  I came to web programming late and
>>went directly to Java, so I tend to not think of things that are second
>>nature to people that have had to wrestle with CGI scripts.   I guess I 
>>can try to do the hidden field thing.   I can make the comment renderer
>>look for those fields and fake an entry for preview.  But it's nasty 
>>ugly.
>>    
>>
>
>Hehe.. I know what you mean... :-P
>
>  
>
>>Don't worry - I'm not advocating building a session mechanism.  But I do
>>think that trying to combine everything into one mega handler (as was 
>>being proposed) is going to have some interesting challenges if we want to try
>>and handle everything that we can do now.
>>    
>>
>
>I can see the headlines *Pyblosxom replaces Zope* and *Pyblosxom, your
>all in one CMS that can plug into your CRM and ERP software.*
>
>Just what is everything?
> * Data representation?
> * Data management?
>
>When I see that people used pyblosxom as some kind of database for
>documents and other wierd stuff (that bonzai -> pyblosxom integration
>counts as the wierdest), I'm not sure what pyblosxom is anymore :)
>
>
>  
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>_______________________________________________
>pyblosxom-users mailing list
>pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>  
>




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click