home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
WindowPlugins bloated?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="pherret" data-source="post: 36926" data-attributes="member: 18369"><p>I'm trying to figure out what the thinking behind bundling all the window plugins in one library was.</p><p></p><p>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.</p><p></p><p>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. </p><p></p><p>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?</p><p></p><p>Thoughts? Comments?</p><p></p><p>If the idea is liked, I'd be happy to submit a patch. The patch might be pretty large though.</p></blockquote><p></p>
[QUOTE="pherret, post: 36926, member: 18369"] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
WindowPlugins bloated?
Contact us
RSS
Top
Bottom