Reply to thread

Message

<blockquote data-quote="jameson_uk" data-source="post: 361444" data-attributes="member: 11220">Been thinking about this for a while now.&nbsp; My view is that Skin choice should definately be through MP.&nbsp;&nbsp; This in itself would not be too difficult and you could browse skins and download one you wanted.&nbsp; (it is posible in the current setup to download and change to a skin without closing and restarting MP isn't it???Plugins however are limited by their interface to MP.&nbsp; It is not simply a case of downloading something, most plugins require quite complex setup and then copying of skin files, ....It should also be easy enough to identify if skins you have installed have been updated and install new versions.&nbsp; This would not however solve the biggest issue in my opinion which is finding skin files for plugins for your skins (or them existing at all).This could be solved by combining the skin files with the plugin files but the skin developers seem to (on the whole) be different people to the plugin developers and then you have the issue of who becomes responsible for maintaining the install package for the plugin...I am begining to think that the best solution might be to keep the split but link them.&nbsp; It would be possible to have a link from a plugin to skin files for that plugin and users could then follow the link to browse skin files (or perhaps the download could include and install the associated skin files that a user selects for that plugin...)I do however feel fairly strongly that plugins and full skins should be kept seperately for simplicity.&nbsp; The idea of building the skins into the MP client seems to be a winner without too much effort ???&nbsp;&nbsp; Going to think about this some more on the way home!!!</blockquote>

[QUOTE="jameson_uk, post: 361444, member: 11220"] Been thinking about this for a while now. My view is that Skin choice should definately be through MP. This in itself would not be too difficult and you could browse skins and download one you wanted. (it is posible in the current setup to download and change to a skin without closing and restarting MP isn't it??? Plugins however are limited by their interface to MP. It is not simply a case of downloading something, most plugins require quite complex setup and then copying of skin files, .... It should also be easy enough to identify if skins you have installed have been updated and install new versions. This would not however solve the biggest issue in my opinion which is finding skin files for plugins for your skins (or them existing at all). This could be solved by combining the skin files with the plugin files but the skin developers seem to (on the whole) be different people to the plugin developers and then you have the issue of who becomes responsible for maintaining the install package for the plugin... I am begining to think that the best solution might be to keep the split but link them. It would be possible to have a link from a plugin to skin files for that plugin and users could then follow the link to browse skin files (or perhaps the download could include and install the associated skin files that a user selects for that plugin...) I do however feel fairly strongly that plugins and full skins should be kept seperately for simplicity. The idea of building the skins into the MP client seems to be a winner without too much effort ??? Going to think about this some more on the way home!!! [/QUOTE]

Verification