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: 6948"><p>What I think should be in place, which i belive i mentioned earlier is that subdirectorys would be enumerated for plugins, which would contain the XML files for the skin, any non standard graphics, and dll/setting files, then when the plugin is loaded it would check the skin directory for plugin_name.xml, if found load that, if not found load local directory one, this way theres a standard interface which is avalaible to all skins, but also gives the skin developer the *option* of having more power to control that plugins interface this way plugins could be released witrhout a NEED to update the skin but as an option to the skin developer.</p><p>There are standard button names already used, maybe create some standard that defines the filename the button/etc is supposto have and what its purpose is so standardise things a little more, example</p><p></p><p>panel.PNG = Panel Frame</p><p>button-nofocus.PNG = Button NOT Focused</p><p>button.PNG = Button Focused</p><p>etc</p><p></p><p>This way plugin developers can use standard image file names in their XML and it would still look good having those standard names so you dont have the problem of well im writing my plugin for XXX skinn which has a blue look to it then if the plugins not implemnented in XXXred skin, it doesnt have a whole red look then all of a sudden blue buttons/etc, it would use the standard skin buttons which would consist of all of mediaportals controls.</p><p></p><p>Also another important part to look at while where here is langauge file, everythime a plugin needs to add another multi-langauge term it has to go in the main langauge file, I would say to extened the mediaportal loading to first check PLUGIN_DIR\strings.XML which would contain all langauge or PLUGIN_DIR\langauge.xml when loading a string from the plugin this way the plugin writer has full control of his string's/string ID's and if any updates are needed he simply realese a new installer/zip file not having to worryt about if his strings.xml file was up to date when he released it or if someone else is simotaniasly adding there own strings for their plugin and using same id's/etc</p><p></p><p>I think this would make MP's skin and plugin interface much better because all items will be in the plugins directory, all that is really needed is subdirectory enumeration and if a plugin uses this new method a check when loading the plugin is plugin_name.xml exists, if yes load it if not load your own copy</p></blockquote><p></p>
[QUOTE="Anonymous, post: 6948"] What I think should be in place, which i belive i mentioned earlier is that subdirectorys would be enumerated for plugins, which would contain the XML files for the skin, any non standard graphics, and dll/setting files, then when the plugin is loaded it would check the skin directory for plugin_name.xml, if found load that, if not found load local directory one, this way theres a standard interface which is avalaible to all skins, but also gives the skin developer the *option* of having more power to control that plugins interface this way plugins could be released witrhout a NEED to update the skin but as an option to the skin developer. There are standard button names already used, maybe create some standard that defines the filename the button/etc is supposto have and what its purpose is so standardise things a little more, example panel.PNG = Panel Frame button-nofocus.PNG = Button NOT Focused button.PNG = Button Focused etc This way plugin developers can use standard image file names in their XML and it would still look good having those standard names so you dont have the problem of well im writing my plugin for XXX skinn which has a blue look to it then if the plugins not implemnented in XXXred skin, it doesnt have a whole red look then all of a sudden blue buttons/etc, it would use the standard skin buttons which would consist of all of mediaportals controls. Also another important part to look at while where here is langauge file, everythime a plugin needs to add another multi-langauge term it has to go in the main langauge file, I would say to extened the mediaportal loading to first check PLUGIN_DIR\strings.XML which would contain all langauge or PLUGIN_DIR\langauge.xml when loading a string from the plugin this way the plugin writer has full control of his string's/string ID's and if any updates are needed he simply realese a new installer/zip file not having to worryt about if his strings.xml file was up to date when he released it or if someone else is simotaniasly adding there own strings for their plugin and using same id's/etc I think this would make MP's skin and plugin interface much better because all items will be in the plugins directory, all that is really needed is subdirectory enumeration and if a plugin uses this new method a check when loading the plugin is plugin_name.xml exists, if yes load it if not load your own copy [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Skin Engine Suggestion
Contact us
RSS
Top
Bottom