Reply to thread

Message

<blockquote data-quote="da-anda" data-source="post: 648913" data-attributes="member: 86409">I'm not sure if a skinning contest as I understood your intention is a good start in first place. Although it would be nice to see some skins available on release of MP2, I'd personally perfer only one skin that's really good instead of several lousy ones (don't mean to offend anybody here). So maybe the contest should not incorporate full working skins, but just wireframes, mockups and UI concepts instead. Users then can vote for those in different categories (like general appealing, ui-concept, features) and after that form a skinning team out of the contest winners, add some core devs to the team, call a team-leader and create a fantastic default skin for mediaPortal. That's how I would do it.As it just came to my mind when talking about skins. PLEASE change the way the handling of skin files works (if not done already). It really sucks if you install a plugin and your skin doesn't support it. There should not be the need for a skin to support certain plugins, nor to copy any XML files to skin directories - this is not userfriendly at all. Plugins should provide default skin files so that they work in any case. If a skin then is providing a optimized version for a plugin, use this one - if not, fall back to the default MP skin files or the plugins generic skin file.If you need some more conceptual ideas/help - let me know <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="da-anda, post: 648913, member: 86409"] I'm not sure if a skinning contest as I understood your intention is a good start in first place. Although it would be nice to see some skins available on release of MP2, I'd personally perfer only one skin that's really good instead of several lousy ones (don't mean to offend anybody here). So maybe the contest should not incorporate full working skins, but just wireframes, mockups and UI concepts instead. Users then can vote for those in different categories (like general appealing, ui-concept, features) and after that form a skinning team out of the contest winners, add some core devs to the team, call a team-leader and create a fantastic default skin for mediaPortal. That's how I would do it. As it just came to my mind when talking about skins. PLEASE change the way the handling of skin files works (if not done already). It really sucks if you install a plugin and your skin doesn't support it. There should not be the need for a skin to support certain plugins, nor to copy any XML files to skin directories - this is not userfriendly at all. Plugins should provide default skin files so that they work in any case. If a skin then is providing a optimized version for a plugin, use this one - if not, fall back to the default MP skin files or the plugins generic skin file. If you need some more conceptual ideas/help - let me know :) [/QUOTE]

Verification