- August 31, 2006
- 2,159
- 2,679
- Home Country
- Sweden
- Moderator
- #21
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
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