making flavours easier III

Hmmm....  Maybe we can make flavours even easier?  Right now, if you
use a plugin, you have to edit the flavour file in the right place:
e.g. pyarchives or pycalendar.  If the plugin results were available
in a structured form, then a meta-plugin could take all those results
and insert them into a flavour in a structured manner.

I imagine a meta-plugin which knows about plugins and then (through some
magic) fetches and inserts their results.  It would be called from a
flavour like this:
    $util::plugins("<li>%(value)s</li>").
or like this:
    $util::plugins("<li>%(name)s:<ul><li>%(value)s</li></ul></li>").
or like this:
    $util::plugins("<p>%(value)s</p>").
or like this:
    $util::plugins("%(value)s<br />").

It would take each of the plugin results and return them in situ.
It would use a new configuration variable to set the order of the
plugins.  No, no, wait, even better: it would look at the order in
which plugins were specified in 'load_plugins'.

The stumbling block to simply writing this as a plugin is that I see
no current way to identify variables created by a plugin.

-- 
--My blog is at     blog.russnelson.com         | The laws of physics cannot
Crynwr sells support for free software  | PGPok | be legislated.  Neither can
521 Pleasant Valley Rd. | +1 315-323-1241 cell  | the laws of countries.
Potsdam, NY 13676-3213  | +1 212-202-2318 VOIP  | 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click