Reply to thread

Message

<blockquote data-quote="JDWestoby" data-source="post: 347694" data-attributes="member: 72093">I've just been writing a plugin and to configure it outside of MediaPortal is a pain, using real windows controls etc. (I did find something on config issues but nothing definite.)Now some things might need this - I certainly couldn't/wouldn't want to set up WebEPG using the onscreen keyboard and no mouse! But most things are quite simple.For mine I needed to save a couple of values and (according to the dev guide) you use a xml file and MP calls.Inside the plugin this is trivial (about 6 lines of code, stolen from SourceForge - thanks guys <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />) and I just dumped a 'Save' button onto the plugin screen.This means you can change it 'on the fly' and just carry on. (OnPageLoad reads the config file.)Maybe this strategy could be useful/used for other plugins too?Also in a simialr generic editor I did a while back, instead of numbers for fields (in the skin XML file) we mapped names which is a lot more intuitive and a lot more understandable. No way is this a sticking point, it's only something you have to do when developing after all!Hope this doesn't tread on anyone's toes, I am VERY impressed with both MediaPortal and the standard of code.</blockquote>

[QUOTE="JDWestoby, post: 347694, member: 72093"] I've just been writing a plugin and to configure it outside of MediaPortal is a pain, using real windows controls etc. (I did find something on config issues but nothing definite.) Now some things might need this - I certainly couldn't/wouldn't want to set up WebEPG using the onscreen keyboard and no mouse! But most things are quite simple. For mine I needed to save a couple of values and (according to the dev guide) you use a xml file and MP calls. Inside the plugin this is trivial (about 6 lines of code, stolen from SourceForge - thanks guys :thx:) and I just dumped a 'Save' button onto the plugin screen. This means you can change it 'on the fly' and just carry on. (OnPageLoad reads the config file.) Maybe this strategy could be useful/used for other plugins too? Also in a simialr generic editor I did a while back, instead of numbers for fields (in the skin XML file) we mapped names which is a lot more intuitive and a lot more understandable. No way is this a sticking point, it's only something you have to do when developing after all! Hope this doesn't tread on anyone's toes, I am VERY impressed with both MediaPortal and the standard of code. [/QUOTE]

Verification