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
Skin Engine Suggestion
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="Anonymous" data-source="post: 6961"><p>Well... I was just throwing out an idea. Here's what my understanding of the situation is based on the replies...</p><p></p><p>1. The skinners WANT to design the UI for each plugin</p><p>2. Most of what I suggested is already in place (just not always adhered to?)</p><p></p><p>Here's the big reason I made the suggestion.. Once (not if) MP goes mainstream, the plugins will proliferate. The possibilities are almost limitless. In a year you could be talking about 100 or more plugins. Do you, as a skinner really want to that amount of work for ONE skin everytime there's a new release? Even assuming that engine stabilizes so each new release doesn't require a skin update, and if you only have to doa plugin once and never look back, it still sounds like a lot of work to me. I think I'd rather remain a bystander.</p><p></p><p>The main idea with the "construction kit" was that each skin could define the image libraries so the the plugin would still use the skin and have that skin's unique look. Yes, the pluging developer does the skin for his/her plugin while maintaining the look and feel of the skin. But unless it's a "core" plugin (if there is any such thing) I don't think I would even want to look at all the possible plugins.</p><p></p><p>I hope I threw a couple of things out for you to think about and conisder. I think in the meantime I am going to see how some of the other projects do it and maybe clarify my suggestion. If not, I'll let it die peacefully. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>Cheers!</p></blockquote><p></p>
[QUOTE="Anonymous, post: 6961"] Well... I was just throwing out an idea. Here's what my understanding of the situation is based on the replies... 1. The skinners WANT to design the UI for each plugin 2. Most of what I suggested is already in place (just not always adhered to?) Here's the big reason I made the suggestion.. Once (not if) MP goes mainstream, the plugins will proliferate. The possibilities are almost limitless. In a year you could be talking about 100 or more plugins. Do you, as a skinner really want to that amount of work for ONE skin everytime there's a new release? Even assuming that engine stabilizes so each new release doesn't require a skin update, and if you only have to doa plugin once and never look back, it still sounds like a lot of work to me. I think I'd rather remain a bystander. The main idea with the "construction kit" was that each skin could define the image libraries so the the plugin would still use the skin and have that skin's unique look. Yes, the pluging developer does the skin for his/her plugin while maintaining the look and feel of the skin. But unless it's a "core" plugin (if there is any such thing) I don't think I would even want to look at all the possible plugins. I hope I threw a couple of things out for you to think about and conisder. I think in the meantime I am going to see how some of the other projects do it and maybe clarify my suggestion. If not, I'll let it die peacefully. :D Cheers! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Skin Engine Suggestion
Contact us
RSS
Top
Bottom