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
Area 51 - Testing Area
Blow WindowPlugins.dll to separate plugin DLLs
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="elliottmc" data-source="post: 1056024" data-attributes="member: 14268"><p>Did we break plugin compatibility in 1.6.0 ?</p><p></p><p>I guess at least with the releases being more frequent, any plugin that is compatible with 1.6.0 is being actively developed so there should in principle not be a problem with getting an updated version.</p><p></p><p>I guess overall, the question is whether we as a team will benefit more from splitting windowsplugins to separate files. If we will (in terms of maintenance of code, stability, etc.) then I think we should just bite the bullet and get it done, as long as the code is properly tested and reviewed.</p><p></p><p>If there aren't enough gains, we could delay for a release, but then there is the risk that some plugins will become unsupported and then not be updated.</p><p></p><p>I will have to be guided by developers in terms of the benefits versus the inconvenience of a little tweak to plugins.</p></blockquote><p></p>
[QUOTE="elliottmc, post: 1056024, member: 14268"] Did we break plugin compatibility in 1.6.0 ? I guess at least with the releases being more frequent, any plugin that is compatible with 1.6.0 is being actively developed so there should in principle not be a problem with getting an updated version. I guess overall, the question is whether we as a team will benefit more from splitting windowsplugins to separate files. If we will (in terms of maintenance of code, stability, etc.) then I think we should just bite the bullet and get it done, as long as the code is properly tested and reviewed. If there aren't enough gains, we could delay for a release, but then there is the risk that some plugins will become unsupported and then not be updated. I will have to be guided by developers in terms of the benefits versus the inconvenience of a little tweak to plugins. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
Blow WindowPlugins.dll to separate plugin DLLs
Contact us
RSS
Top
Bottom