[mythtv] Revamping the plugin system.

Isaac Richards ijr at po.cwru.edu
Thu Nov 27 19:19:12 EST 2003


On Thursday 27 November 2003 06:54 pm, J. Donavan Stanley wrote:
> Isaac Richards wrote:
> >On Thursday 27 November 2003 01:42 pm, J. Donavan Stanley wrote:
> >>There's a piece of the puzzle I left out, the PluginLoader... If you
> >>want your plugins in C, it'd be trival to implment a PluginLoader that
> >>creates the required interface by using pointers to exported functions,
> >>much in the way I currently do it for legacy plugins.  If you want them
> >>in some sort of scripting language, then once you've got bindings done,
> >>via SWIG or what have you, then create a loader that can load plugins
> >>from scripts as well.  The new system doesn't lose any existing
> >>functionality or flexibility only adds it.  The discovery of plugins is
> >>done by the PluginManager via it's register PluginLoaders.  The
> >>PluginManager doesn't care where the plugins come from just that there's
> >>a mechanism to get Plugin* from a plugin loader.
> >
> >You're overdesigning things horribly.  Simple is best, always.
>
> hrm ok...  Glad I got your opinion before trying to submit this stuff
> then.  I'm curious though, if four objects or so that provide a
> constistant estensible frame work for plugins is an overdesign, what's
> your plan for plugins?

If you want major changes, you need to prove that they're needed.  Nothing 
that you've described can't be done within the existing framework, or with 
small extensions to it like Thor's already done for mfd, or even like what 
I've done in the past few days with the jump point stuff.

Isaac


More information about the mythtv-dev mailing list