Reply to thread

Message

<blockquote data-quote="Baboonanza" data-source="post: 712151" data-attributes="member: 101901">How easy it is to migrate from MP1 to MP2 is dependant on exactly what the plugin does, so it's difficult to give a clear answer. Basically the more GUI stuff is in it the more effort it will be to migrate. If all of the difficult code is doing something in the back-end then that code can just be used in MP2 and the coversion cost will be small. My opinion is that MP2 plugins can actually be simpler in a lot of cases becase there is less farting around with GUI elements directly in the code, but then I'm an MP2 developer so I would say that <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I would suggest making it for MP1, but having a quick look at plugins for MP2 (Weather is simplest) to get rough idea how they work so that you can write it in a way that makes transition easier later.</blockquote>

[QUOTE="Baboonanza, post: 712151, member: 101901"] How easy it is to migrate from MP1 to MP2 is dependant on exactly what the plugin does, so it's difficult to give a clear answer. Basically the more GUI stuff is in it the more effort it will be to migrate. If all of the difficult code is doing something in the back-end then that code can just be used in MP2 and the coversion cost will be small. My opinion is that MP2 plugins can actually be simpler in a lot of cases becase there is less farting around with GUI elements directly in the code, but then I'm an MP2 developer so I would say that :) I would suggest making it for MP1, but having a quick look at plugins for MP2 (Weather is simplest) to get rough idea how they work so that you can write it in a way that makes transition easier later. [/QUOTE]

Verification