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 2
Skins and Design
Design Guidelines - Best Practices
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="chefkoch" data-source="post: 1035024" data-attributes="member: 10438"><p>@[USER=48495]morpheus_xx[/USER] @[USER=118429]wizard123[/USER] @[USERGROUP=38]Designers[/USERGROUP] </p><p></p><p>Could we collect, maybe in wiki (if it is not there yet), kind of best practices for designers and devs as well?</p><p>This way plugin devs might already be able to keep things for designers in mind when they write the plugin code.</p><p></p><p>There might always be things that depend on the skin, but other might apply to skinning and design in general.</p><p></p><p>Here I have a first example: <a href="https://github.com/BigGranu/Webradio_MP2/issues/10" target="_blank">https://github.com/BigGranu/Webradio_MP2/issues/10</a></p><p>What is the best way to handle such cases? Hide the label, add a fallback text ??</p><p></p><p>Again, I know this might be different from skin to skin, but maybe for the default skin files we should handle such things consistent through all plugins to improve the user experience.</p></blockquote><p></p>
[QUOTE="chefkoch, post: 1035024, member: 10438"] @[USER=48495]morpheus_xx[/USER] @[USER=118429]wizard123[/USER] @[USERGROUP=38]Designers[/USERGROUP] Could we collect, maybe in wiki (if it is not there yet), kind of best practices for designers and devs as well? This way plugin devs might already be able to keep things for designers in mind when they write the plugin code. There might always be things that depend on the skin, but other might apply to skinning and design in general. Here I have a first example: [url]https://github.com/BigGranu/Webradio_MP2/issues/10[/url] What is the best way to handle such cases? Hide the label, add a fallback text ?? Again, I know this might be different from skin to skin, but maybe for the default skin files we should handle such things consistent through all plugins to improve the user experience. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Skins and Design
Design Guidelines - Best Practices
Contact us
RSS
Top
Bottom