I haven't tried it yet, but read the source. Some suggestions:
Maybe you shouldn't add the ripper to the main menu, maybe an item plugin is the better way. Pressing ENTER on an audio cd will give you the item ('rip to harddisc'). See cover_search.py for an example of an item plugin for audiocds.
I think this as an Item plugin would be nice as well.
Question to everyone: how should we deal with plugin options? Should we place them into freevo_config.py even when some people don't need them? Even when the plugin is not active as default? Or should we make
Right, perhaps we shouldn't clutter up freevo_config.py like this.
it a long parameter list like
plugin.activate('name', args=('%(artist)s/%(album)s/%(song)s', ...))
Or should we make it like now: a plugin description should also contain a list of variables the plugin needs? How to print this information to the user?
Right now I am partial to having a list of required config items and examples in the header of the plugin as a comment. Then the user would be required to add them to local_conf.py. But now that you have me thinking about it... plugin arguments may be cleaner and easier to have default parameters.
I will do some experimenting with the ivtv recording plugin with options as parameters. This would make it easier to add plugins without worying about freevo_config.py and should keep freevo from crashing because someone activated a plugin and didn't add any new config items.
-Rob
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
