I'm trying to figure out what the thinking behind bundling all the window plugins in one library was.
My understanding on the current code is that it searchs the plugins/windows directory (and other directories) for plugins and if they are enabled, load them. My CVS build has three dlls. The monster dll, WindowPlugins.dll, contains a LOT of plugins. Some of them not working entirely.
Shouldn't the approach be that each plugin is its own dll? This way, only the *actual* enabled plugins are loaded and the disabled ones are not loaded. Also, team-mediaportal doesn't need to manage all the plugins.
I've already begun separating out the plugins into separate VS projects and configuring the references and build directories. Am I helping out or am I reversing something good?
Thoughts? Comments?
If the idea is liked, I'd be happy to submit a patch. The patch might be pretty large though.
My understanding on the current code is that it searchs the plugins/windows directory (and other directories) for plugins and if they are enabled, load them. My CVS build has three dlls. The monster dll, WindowPlugins.dll, contains a LOT of plugins. Some of them not working entirely.
Shouldn't the approach be that each plugin is its own dll? This way, only the *actual* enabled plugins are loaded and the disabled ones are not loaded. Also, team-mediaportal doesn't need to manage all the plugins.
I've already begun separating out the plugins into separate VS projects and configuring the references and build directories. Am I helping out or am I reversing something good?
Thoughts? Comments?
If the idea is liked, I'd be happy to submit a patch. The patch might be pretty large though.