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
Plugins for Mediaportal Important!
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="tourettes" data-source="post: 342366" data-attributes="member: 10858"><p>The problem is not as easy as it sounds. There are many things that contribute to the fact that we dont want to provide any skin files for 3rd party plugins</p><p></p><p>I - Extra work it causes, currently Harley is working almost alone on the B3/B3W so he has already too much workload</p><p></p><p>II - If we provide .xml files for only some 3rd party plugins other plugin devs will feel they should have the same threatment -> as a result there will be nagging <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>III - We cannot distribute the 3rd party plugin .xml files with the applications as they would get out dated at some point (most likely pretty soon) as the plugins itself are envolving)</p><p></p><p>IV - When developer creates a plugin hé should be able to create some sort of skin files (for B3/B3W at least. Skin developers should be using those as the starting point for 1) making the B3/B3W skin files better 2) providing support for other skins)</p><p></p><p>...so, if developer is not able to provide skin files for the default B3/B3W skin he/she should ask some skinner in the MP community to provide such files that then can be distributed within the plugin installation (preferably MPI)</p></blockquote><p></p>
[QUOTE="tourettes, post: 342366, member: 10858"] The problem is not as easy as it sounds. There are many things that contribute to the fact that we dont want to provide any skin files for 3rd party plugins I - Extra work it causes, currently Harley is working almost alone on the B3/B3W so he has already too much workload II - If we provide .xml files for only some 3rd party plugins other plugin devs will feel they should have the same threatment -> as a result there will be nagging :) III - We cannot distribute the 3rd party plugin .xml files with the applications as they would get out dated at some point (most likely pretty soon) as the plugins itself are envolving) IV - When developer creates a plugin hé should be able to create some sort of skin files (for B3/B3W at least. Skin developers should be using those as the starting point for 1) making the B3/B3W skin files better 2) providing support for other skins) ...so, if developer is not able to provide skin files for the default B3/B3W skin he/she should ask some skinner in the MP community to provide such files that then can be distributed within the plugin installation (preferably MPI) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Plugins for Mediaportal Important!
Contact us
RSS
Top
Bottom