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 Plugins
MPEM Development Info & Testversion
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="mm1352000" data-source="post: 1022611" data-attributes="member: 82144"><p>Thanks for the quick response! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p></p><p>I am definitely in support of MPEM handling them. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p></p><p>Okay. I'm not sure if you were already aware of the other thread or if you were following the internal release process for MP 1.5 PR? Basically there has been some discussion about how to handle skin updates, whether skin files should be distributed in the skin or plugin packages etc. etc.</p><p>As the main MPEM developer/designer I hope you are aware that these conversations are happening and that they are giving some understanding of the complexity of the requirements for MPEM... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p></p><p>Yes, this install package type is critical for skins and logos in particular because I think they have more complex requirements than plugins.</p><p>For skins it may be desirable to have per-plugin [sub]packages (ie. distributions of only the files for a particular plugin + skin combination) and/or update packages in addition to full skin release packages.</p><p>For logos it may be desirable to have separate packages by style, location (regions/country), provider. At least it is not always desirable to download a huge package of logos if you're only interested in a small subset.</p><p> </p><p>I'm not saying that I understand all or even any of the requirements for these things - far from it. Just looking to try and bring together people who are working on and/or talking about similar topics so that there is potential for co-operation. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="mm1352000, post: 1022611, member: 82144"] Thanks for the quick response! :) I am definitely in support of MPEM handling them. :) Okay. I'm not sure if you were already aware of the other thread or if you were following the internal release process for MP 1.5 PR? Basically there has been some discussion about how to handle skin updates, whether skin files should be distributed in the skin or plugin packages etc. etc. As the main MPEM developer/designer I hope you are aware that these conversations are happening and that they are giving some understanding of the complexity of the requirements for MPEM... :) Yes, this install package type is critical for skins and logos in particular because I think they have more complex requirements than plugins. For skins it may be desirable to have per-plugin [sub]packages (ie. distributions of only the files for a particular plugin + skin combination) and/or update packages in addition to full skin release packages. For logos it may be desirable to have separate packages by style, location (regions/country), provider. At least it is not always desirable to download a huge package of logos if you're only interested in a small subset. I'm not saying that I understand all or even any of the requirements for these things - far from it. Just looking to try and bring together people who are working on and/or talking about similar topics so that there is potential for co-operation. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
MPEM Development Info & Testversion
Contact us
RSS
Top
Bottom
