Hi,
I just changed some stuff for plugins and how to write one. When I
wrote the plugin system, I added 'args' to set arguments for a
plugin. But most plugins set the arguments by added variables to
freevo_config.py. I agree, this is the better way. However, writing a
plugin means not only adding the plugin to the dir, also changing
freevo_config.py. The result is that this file gets bigger and bigger
and new users have more stuff to check. Even worse: they check
variables for plugins that are not even activated. This is bad.
I changed the cdbackup audio plugin to the new guidelines I want like
to establish (comments welcome):
1. each plugin needs a good description to work with the 'freevo
plugin' helper. This includes a short description (one line),
followed by an empty line and a long description. See my mail from
yesterday about the descriptions.
2. a plugin that is not activated by default and needs variables from
config, shouldn't add them to freevo_config.py, they should use the
new config() function for plugins:
def config(self):
return (('VARNAME', 'default value', 'description'), (...))
The description is not needed right now, but may be usefull for a
future configuration tool. In __init__ of the plugin the varaibles
will be added to config if tehy aren't defined (== the user has no
private settings in local_conf.py)
Dischi
--
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" but "That's funny..."' - Isaac Asimov
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
