Reply to thread

Message

<blockquote data-quote="offbyone" data-source="post: 1056243" data-attributes="member: 73415">I don't think it is the plugin devs opinion you need. It's more about the users. Active plugin devs can release a new version, since the change is not that big, most likely nothing to implement, only change references and recompile and release a new version. but this new version will only be compatible with new MP 1.7 then. And I will not maintain two branches. I have seen many questions by users that they are using old MP version and want to know how to run latest OnlineVideos on it. So in the end you are only annoying the users and forcing them to update. But many older non-maintained plugins are used by the users and that is why many don't like updating, as on of their used plugins is no longer available then. Personally, I don't care if it's included or not. As said I am no longer taking active part in MP1 development, so as plugin dev I will update OV and do a new release.As a user I'd ask: WHY the hell do you break plugin compatibility for no reason? All I see is that there are more dlls, but no added benefit for me <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Note to seco:This is nothing against this change from my perspective as a developer. It is a good thing to split the plugins into assemblies (heck you are trying to make MP1 more like MP2 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> ) - but it is really late in the life cycle, that's where the troubles come from.</blockquote>

[QUOTE="offbyone, post: 1056243, member: 73415"] I don't think it is the plugin devs opinion you need. It's more about the users. Active plugin devs can release a new version, since the change is not that big, most likely nothing to implement, only change references and recompile and release a new version. but this new version will only be compatible with new MP 1.7 then. And I will not maintain two branches. I have seen many questions by users that they are using old MP version and want to know how to run latest OnlineVideos on it. So in the end you are only annoying the users and forcing them to update. But many older non-maintained plugins are used by the users and that is why many don't like updating, as on of their used plugins is no longer available then. Personally, I don't care if it's included or not. As said I am no longer taking active part in MP1 development, so as plugin dev I will update OV and do a new release. As a user I'd ask: WHY the hell do you break plugin compatibility for no reason? All I see is that there are more dlls, but no added benefit for me ;) Note to seco: This is nothing against this change from my perspective as a developer. It is a good thing to split the plugins into assemblies (heck you are trying to make MP1 more like MP2 ;) ) - but it is really late in the life cycle, that's where the troubles come from. [/QUOTE]

Verification