From: Dennis S. <sy...@yo...> - 2004-09-02 06:16:39
|
I have moved it into the plugin specific data structure and I totally think it belongs here (VisActorPlugin etc etc) This way generic plugins can be created as well, for libvisual-display for example. Cheers, Dennis On Wed, 2004-09-01 at 23:28 -0300, Duilio Javier Protti wrote: > > /** > > * The VisPluginInfo data structure contains information about a plugin > > * and is filled within the plugin itself. > > */ > > struct _VisPluginInfo { > > > > ..... > > > > /* FIXME do we move prefs to the separate plugin structures, or > > do we move everything (the methods as well) into an union here ? */ > > union { > > struct { > > int depth; > > } actor; > > > > struct { > > int depth; > > } morph; > > } prefs; > > > > }; > > I think would be good to move prefs to _VisPluginData, because it is > data subject to change on the fly. This way we kept all 'static' info on > _VisPluginInfo and 'dynamic' plugin info go to _VisPluginData. > > Bye, > Duilio. |