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: 1056033" data-attributes="member: 14268"><p>I fear that if we don't merge this for 1.7.0, it will get so much harder to merge to the point where we lose the will to do it, and it becomes one of many branches we have that would be great to include but too much effort.</p><p></p><p>If we do merge this, there is absolutely no chance that a plugin will be able to support 1.6.0 and 1.7.0 in a single binary version, right?</p><p></p><p>Personally I don't see any reason for users not to run the latest version. Did we break anything so badly in 1.6.0 that a significant number of users don't want to upgrade? Even if this is the case (which I don't think it is), presumably those users would also be happy with the older versions of the plugins, so we would encourage community plugin developers to focus on the latest and greatest. It seems that many people are spending a lot of effort supporting older versions of software (which we do to some extent with the OS, including XP support which we have now ditched).</p></blockquote><p></p>
[QUOTE="elliottmc, post: 1056033, member: 14268"] I fear that if we don't merge this for 1.7.0, it will get so much harder to merge to the point where we lose the will to do it, and it becomes one of many branches we have that would be great to include but too much effort. If we do merge this, there is absolutely no chance that a plugin will be able to support 1.6.0 and 1.7.0 in a single binary version, right? Personally I don't see any reason for users not to run the latest version. Did we break anything so badly in 1.6.0 that a significant number of users don't want to upgrade? Even if this is the case (which I don't think it is), presumably those users would also be happy with the older versions of the plugins, so we would encourage community plugin developers to focus on the latest and greatest. It seems that many people are spending a lot of effort supporting older versions of software (which we do to some extent with the OS, including XP support which we have now ditched). [/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