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
MediaPortal 1 Plugins
Standard GUI properies for Plugin Developers
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="Dadeo" data-source="post: 515454" data-attributes="member: 27204"><p>In <a href="https://forum.team-mediaportal.com/moving-pictures-284/no-itemcount-70278/" target="_blank">MovingPictures - No Itemcount</a> Pilehave has raised the very important point that #itemcount is not supported. I have found this is true in many community plugins and suggested there could be some standard kit of GUI properties that should always be supported in plugins.</p><p></p><p>Would this be helpful to Plugin Developers?</p><p></p><p>If so, how do we proceed? One way is to have skinners list in this thread the properties they think should always be supported. I don't think it is fair to expect the MP Developers to know what properties we want/need.</p><p></p><p>Pilehave has also suggested the "write your own plugin" tutorial in the Wiki could be improved. An excellent suggestion, but who is going to do this? To be honest I think that some skinners probably know as much or more about the skin engine as a lot of developers at this point. If you haven't skinned you cannot write good user documentation on skinning. But even skinners have trouble knowing everything about the skin engine or how properties work in various cases. Hence the problem in the WIKI.</p><p></p><p>I have always thought that plugin developers should work with skinners when developing new plugins. Wherever this has happened I think the results have been good. But it is not practical. I see Plugin Developers asking for help from skinners, but no response - because most skinners can barely manage as it is <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>So my temporary suggestion is let's give Plugin Developers some tips here to start, and see if we cannot come up with a list of standard GUI Properties that should be supported in any plugin.</p><p></p><p>Then we can use that to update the WIKI. Any other suggestions would be greatly appreciated.</p><p></p><p>Pilehave has started us off with</p><p>1.#itemcount</p><p>2.#selecteditem </p><p>3.#selectedthumb</p></blockquote><p></p>
[QUOTE="Dadeo, post: 515454, member: 27204"] In [URL="https://forum.team-mediaportal.com/moving-pictures-284/no-itemcount-70278/"]MovingPictures - No Itemcount[/URL] Pilehave has raised the very important point that #itemcount is not supported. I have found this is true in many community plugins and suggested there could be some standard kit of GUI properties that should always be supported in plugins. Would this be helpful to Plugin Developers? If so, how do we proceed? One way is to have skinners list in this thread the properties they think should always be supported. I don't think it is fair to expect the MP Developers to know what properties we want/need. Pilehave has also suggested the "write your own plugin" tutorial in the Wiki could be improved. An excellent suggestion, but who is going to do this? To be honest I think that some skinners probably know as much or more about the skin engine as a lot of developers at this point. If you haven't skinned you cannot write good user documentation on skinning. But even skinners have trouble knowing everything about the skin engine or how properties work in various cases. Hence the problem in the WIKI. I have always thought that plugin developers should work with skinners when developing new plugins. Wherever this has happened I think the results have been good. But it is not practical. I see Plugin Developers asking for help from skinners, but no response - because most skinners can barely manage as it is :) So my temporary suggestion is let's give Plugin Developers some tips here to start, and see if we cannot come up with a list of standard GUI Properties that should be supported in any plugin. Then we can use that to update the WIKI. Any other suggestions would be greatly appreciated. Pilehave has started us off with 1.#itemcount 2.#selecteditem 3.#selectedthumb [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Standard GUI properies for Plugin Developers
Contact us
RSS
Top
Bottom