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 Skins
BlueTwo reskinned for 1280x720 (mp .2.0.4)
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="knutinh" data-source="post: 78404" data-attributes="member: 14776"><p>This may be the wrong thread.</p><p></p><p>But I cant help but thinking that there must be some "low level engine adjustements" that will let the skin designers focus on making.... Good skins, while not thinking too much about screen res?</p><p></p><p>It sounds like a waste of the valuable designer time to maintain both a 1280x720 and a 1366x768 skin? Artwork should be made in very high-resolution PSD files, then downsampled to the actual resolution just-in-time? What about shipping SVG vector files, then rendering them as PNG just before the rendering engine kicks in?</p><p></p><p>Then designers could focus on artwork, relative object placement (in percent in stead og pixels), font size etc. </p><p></p><p>I am sure that "handtweaking" is necessary to get optimal results (because small icons look better when hand painted at the right resolution rather than some downsize algo), and because sharpness vs objectsize changes as one goes from VG to 1080p resolution. But anyways....</p><p></p><p>Also, som kind of "fallback" could be beneficial. Since it seems that the current engine does not allow the different skins to be very different on a functional level, it would be practical to fallback to BlueTwo for newly implemented functions keeping functionality in every case, then when the selected skin is updated, the looks would be consistant?</p><p></p><p>regards</p><p>Knut</p></blockquote><p></p>
[QUOTE="knutinh, post: 78404, member: 14776"] This may be the wrong thread. But I cant help but thinking that there must be some "low level engine adjustements" that will let the skin designers focus on making.... Good skins, while not thinking too much about screen res? It sounds like a waste of the valuable designer time to maintain both a 1280x720 and a 1366x768 skin? Artwork should be made in very high-resolution PSD files, then downsampled to the actual resolution just-in-time? What about shipping SVG vector files, then rendering them as PNG just before the rendering engine kicks in? Then designers could focus on artwork, relative object placement (in percent in stead og pixels), font size etc. I am sure that "handtweaking" is necessary to get optimal results (because small icons look better when hand painted at the right resolution rather than some downsize algo), and because sharpness vs objectsize changes as one goes from VG to 1080p resolution. But anyways.... Also, som kind of "fallback" could be beneficial. Since it seems that the current engine does not allow the different skins to be very different on a functional level, it would be practical to fallback to BlueTwo for newly implemented functions keeping functionality in every case, then when the selected skin is updated, the looks would be consistant? regards Knut [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
BlueTwo reskinned for 1280x720 (mp .2.0.4)
Contact us
RSS
Top
Bottom