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
Request for generic menu items between skins
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="cul8er" data-source="post: 664120" data-attributes="member: 24508"><p>Hi,</p><p></p><p>For me every skin editor that want to support the generic settings file is responsible for;</p><p>1. Load the settings file from MediaPortal config directory (be able to parse it)</p><p>2. Save any adjustment an user do in the editor to that same settings file.</p><p>3. Write a basichome.xml file for the skin that the editor supports.</p><p></p><p>In other words. We only need to agree;</p><p>1. What is the filename of the settings file</p><p>2. What is the xml file to look like</p><p></p><p>Then we are done.</p><p></p><p>The plugin id's are loaded dynamically in every editor I have tried today (like StreamedMP, Aeon, X-Factor) so no need for an additional window id file.</p><p></p><p>I'm sorry if I'm a bit harsh here but I think the original idea that a bunch of skins "bought into" with a common settings file is to good and important to drift away from but that's only my two cents. I'll keep quiet now <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>best regards</p><p>cul8er</p></blockquote><p></p>
[QUOTE="cul8er, post: 664120, member: 24508"] Hi, For me every skin editor that want to support the generic settings file is responsible for; 1. Load the settings file from MediaPortal config directory (be able to parse it) 2. Save any adjustment an user do in the editor to that same settings file. 3. Write a basichome.xml file for the skin that the editor supports. In other words. We only need to agree; 1. What is the filename of the settings file 2. What is the xml file to look like Then we are done. The plugin id's are loaded dynamically in every editor I have tried today (like StreamedMP, Aeon, X-Factor) so no need for an additional window id file. I'm sorry if I'm a bit harsh here but I think the original idea that a bunch of skins "bought into" with a common settings file is to good and important to drift away from but that's only my two cents. I'll keep quiet now ;) best regards cul8er [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Request for generic menu items between skins
Contact us
RSS
Top
Bottom