From: Dennis S. <sy...@yo...> - 2004-06-08 11:59:33
|
I'd like to begin working on plugin opts soonish. Opts are plugin parameters which can be used to set intergral, boolean and string values. Opts shouldn't be confused with plugin preferences. Opts are more like low level settings for example: visual_opts_set_string (opts, "gst-pipe", "random ! gst ! pipe"); for a gstreamer actor plugin. (which for example could be streaming video into libvisual). or visual_opts_set_boolean (opts, "displacement", FALSE); that could be disabling the displacement field of the JESS plugin so JESS can be directly drawn in the goom plugin using a special visualFX wrapper for goom. When implementing opts within plugins always keep in mind strongly that opts are meant for low levelness not for preferences. Also I'd like two sets of opts, being local opts and global opts. Libvisual will have a small set of global opts. These are opts that count for EVERY plugin and EVERY plugin should be monitoring these opts. An example on this is a "show songinfo" opts which can be toggled to enable and disable showing songinfo within plugins, when they support this. Local opts are ofcourse plugin specific opts. On the naming, what would you people prefer, "opts", "param" or something else ? Cheers, Dennis |