Re: registry plugin

My main use case was that I needed to re-work the Lyntin code repository 
because it was hacked together in PHP, I am not very well versed in PHP, 
and it lacked a bunch of features that I was really dragging my feet to 
implement.  Then one sunny day I noticed that blosxom had a plugin 
registry and that it was implemented as a blosxom plugin and I said to 
myself, "Self, you can do that."  So I did.

Essentially it just organizes a bunch of registered plugins (in the case 
of Lyntin) so that users in the Lyntin community can see all the plugins 
and sort them by author, date (in case there are upgrades), and category.  
This allows them to get a handle on what plugins are out there and maybe 
what plugins are missing--things that they might want to sit down and 
write because they have a need for functionality that doesn't exist.

That's pretty much what's there.

I have a running example of it at:

  http://www.bluesock.org/~willg/cgi-bin/pyblosxom.cgi/registry.registry


There's more details in the actual code and in the doc-string.  It suits 
my needs already (except for the lack of submission script and the data 
file format is kind of sucky--Wari had some ideas about fixing that which 
I'm going to look into).  I figure if it's useful for anyone else, they're 
welcome to it.  I use it for plugin registry, but it could easily be used 
to index and provide details about other things.

Hope that helps!

/will


On Mon, 14 Apr 2003, Francois Granger wrote:

> At 09:27 -0500 14/04/2003, in message [pyblosxom-users] registry 
> plugin, will wrote:
> >I wrote a registry plugin.
> 
> Sorry if I look stupid, maybe it is because I am just digesting after 
> dinner ;-)
> 
> Can you explain a little more what is the intent, and how to use it ?
> 
> If I understand a little more, I am willing to help with testing.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf