Re: Some plugins and stuff

On Jan 6, 2004, at 8:27 AM, Jesse Lawrence wrote:

> Hello all,
> I've been busy coding some different Pyblosxom
> goodies.  I wanted to show them to everyone before I
> put them in the registry.
>
> acronym.py is a plugin which replaces acronyms with
> <acronym title="definition">acronym</acronym>.  It
> reads the defined acronyms and their definitions from
> a file in your datadir.
> http://mdev.sourceforge.net/jesse/pyblosxom/acronym.py
>

Could this be generalized along the lines of what Blake and Will have 
bee talking about?

> m3u.py is an entryparser which renders m3u playlists
> as an html list.  Very handy when you want to display
> a list of songs.
> http://mdev.sourceforge.net/jesse/pyblosxom/m3u.py

Cool idea -- I'd like to do something like this for the OS X iTunes 
currently playing song.

>
> atom.tar.gz is a plugin (atom.py) and collection of
> atom flavour files for producing Atom 0.3 feeds.  I'd
> like very much to make this plugin as good as
> possible, anyone who has suggestions, feel free to
> contribute.
> http://mdev.sourceforge.net/jesse/pyblosxom/atom.tar.gz
>

This is the one that I looked at the most.  If I look at cb_prepare, 
you're essentially inventing new atom_* names for variables that 
already exist in pyblosxom.  I'm not really sure that this is 
necessary, but I don't think it does any harm.  The two big value adds 
that I see are the get_newest_entry function and the html stripper for 
the summary.

I need to refresh myself on the details of Atom 0.3, since I did my 
atom flavors for 0.2 and then ignored atom while I was writing my book. 
  The big things that are hard to handle are the modes (xml, escaped, 
base64).   We may also want to fill in atom:created, atom:issued (not 
clear what this means), and atom:modified.

I've also been looking at IWS's plugins (sorry to to have detailed 
feedback yet), and I've noticed that a number of plugins are asking for 
a "newest entry" or "newest comment" service from pyblosxom.  It's 
probably worth it to either build this into the core, or implement 
these as standard plugins that other plugins can use.  That way we can 
eliminate duplication among plugins, and provide useful services for 
plugin writers.

Jesse, I'm interested in doing some work with you on this if you like.  
I'm also interested in doing some work on Atom API support.  But the 
first thing on my list is to try to refactor out some of the stuff 
thats common between pyblosxom.py and the various comment related cgis 
and plugins.

> entrybsddb.py is a caching mechanism.  I'm not sure of
> it's worth, and it's probably slower than entrypickle
> or entryshelve.  I just wanted to see what I could
> come up with.
> http://mdev.sourceforge.net/jesse/pyblosxom/entrybsddb.py
>
I didn't really look at this one
> I'd like peoples input and thoughts on these plugins.
> Please feel free to tell me if they suck, or if and
> how they can be made better.
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
----
Ted Leung                          Blog: http://www.sauria.com/blog
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click