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: 7008"><p>well the idea I had would solve both problems, it would allow skin developers complete and full control over the interface, if they wanted, but if the default interface of the plugin looks good and was what they were thinking of implementing, then they can just leave it using the plugins default interface, its the besxt of both worlds, easyness of skin developement without having to code all plugins XML files themselves and the ability to completely customise the interface by using there own XML files, its completely backwords compatible witht he way things are now, so its not forcing all plugin writers to re-package there plugins, and if I understand what MrMario said about the refrences.xml we woulnt even have to specify images in the plugins defaul XML file, so image loading wouldnt even be a problem, all we would need would be sub-directory enumaration when scanning for plugins, its not really even needed but i would like having all plugin binarys, default plugin layout xml, plugin settings xml, etc all in one directory, it would just get too messy also if i release a plugin it can just be a seprate download, install all files to PLUGIN_DIR\Plugin Name\ rather then install some there, some in all the skins directory, some in the langauge file directory hopefully not overrideng someone else langauge changes, I think plugins/skins should be seprate downloads, not from the main MP installation except the main 4 skins, main plugins like weather, as plugin count grows its going to be impracticle to just keep packaging with the main download, MP is a 16MB download as it is, as we keep adding plugins people arent going to want to download a 50MB mediacenter then have to scroll through a hunder plugins, I think they should scroll through a webpage, find the plugins they want download the package and install, same thing for skins, not having to worry if skin A supports plugin B and if it doesnt getting an Error can t find blah.XML</p></blockquote><p></p>
[QUOTE="Anonymous, post: 7008"] well the idea I had would solve both problems, it would allow skin developers complete and full control over the interface, if they wanted, but if the default interface of the plugin looks good and was what they were thinking of implementing, then they can just leave it using the plugins default interface, its the besxt of both worlds, easyness of skin developement without having to code all plugins XML files themselves and the ability to completely customise the interface by using there own XML files, its completely backwords compatible witht he way things are now, so its not forcing all plugin writers to re-package there plugins, and if I understand what MrMario said about the refrences.xml we woulnt even have to specify images in the plugins defaul XML file, so image loading wouldnt even be a problem, all we would need would be sub-directory enumaration when scanning for plugins, its not really even needed but i would like having all plugin binarys, default plugin layout xml, plugin settings xml, etc all in one directory, it would just get too messy also if i release a plugin it can just be a seprate download, install all files to PLUGIN_DIR\Plugin Name\ rather then install some there, some in all the skins directory, some in the langauge file directory hopefully not overrideng someone else langauge changes, I think plugins/skins should be seprate downloads, not from the main MP installation except the main 4 skins, main plugins like weather, as plugin count grows its going to be impracticle to just keep packaging with the main download, MP is a 16MB download as it is, as we keep adding plugins people arent going to want to download a 50MB mediacenter then have to scroll through a hunder plugins, I think they should scroll through a webpage, find the plugins they want download the package and install, same thing for skins, not having to worry if skin A supports plugin B and if it doesnt getting an Error can t find blah.XML [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Skin Engine Suggestion
Contact us
RSS
Top
Bottom