Reply to thread

Message

<blockquote data-quote="infinite.loop" data-source="post: 360438" data-attributes="member: 10723">Blue3 and Blue3wide are the skins which were shipped with MP.That community plugins have to support these at least is a logical consequence if you ask me.It is also in the interest of the users because they do not have to start searching for community skins which support this plugin, if they just want to test it.Right now, every Blue3 and Blue3wide user is forced to change to a skin he might not like just because it does not even support the shipped skins. This could also mean that other plugins he uses nolonger work because they are not supported in this skin, or the skin contains bugs which the user does not encounter in B3(w).Adding B3(w) skin support for &quot;every community plugin&quot; into MediaPortal is a stupid idea (we learned form our misstakes in the past <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />).You just have to compare the release cycles of community plugins and MediaPortal stable releases.We can not release a new stable build everytime when a new plugin is released.And on top of that, the only active skin designer we have in the team is harley. who is devinitly not able to create and maintain support for every community plugin.And creating a basic skin is not a problem for any developer. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="infinite.loop, post: 360438, member: 10723"] Blue3 and Blue3wide are the skins which were shipped with MP. That community plugins have to support these at least is a logical consequence if you ask me. It is also in the interest of the users because they do not have to start searching for community skins which support this plugin, if they just want to test it. Right now, every Blue3 and Blue3wide user is forced to change to a skin he might not like just because it does not even support the shipped skins. This could also mean that other plugins he uses nolonger work because they are not supported in this skin, or the skin contains bugs which the user does not encounter in B3(w). Adding B3(w) skin support for [I]"every community plugin"[/I] into MediaPortal is a stupid idea [I](we learned form our misstakes in the past ;)).[/I] You just have to compare the release cycles of community plugins and MediaPortal stable releases. We can not release a new stable build everytime when a new plugin is released. And on top of that, the only active skin designer we have in the team is harley. who is devinitly not able to create and maintain support for every community plugin. And creating a [U][COLOR="Red"]basic[/COLOR][/U] skin is not a problem for any developer. ;) [/QUOTE]

Verification