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
Support
Skins and Plugins Installer (MPEI)
The future of MPI - we need your opinion!
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="Dadeo" data-source="post: 359947" data-attributes="member: 27204"><p>Yes!!!! I am fully in support of some standard installer for plugins AND skins. </p><p></p><p>When I first loaded MP (before MPI existed) I really did not think it was going to be a good program. At that time, even the main installation was not very good. And what I had to go through to figure out how to install plugins and skins. Well it just didn't look very professional and did not reflect the quality of MP (which is my favorite software EVER). The new Installation is MUCH better, but the plugins and skins... need I say more?</p><p></p><p>I agree with Revs, the best option would be in the main application, but if not, then the MPI tab under Plugins should take you there directly (hopefully without exiting the main configuration! and return you to configuration when you are done or give you an option to exit)</p><p></p><p>So here are my suggestions of what you can do in the near future:</p><p></p><p>1. Link MPI to main plugin (tab) AND skin configuration (I can't find any reference to MPI under Skin Configuration)</p><p></p><p>2. Call it something more user friendly than MPI, like Plugin Installation, Skin Installation (Extensions is becoming more widley used, so that might work!)</p><p></p><p>3. Have an option to check the repository for plugin/skin updates that match your current release of MP (I think the Check for Updates checks for updates to MPI? I'm not sure)</p><p></p><p>3. Get rid of the icons in the current MPI tab under Plugin Conifiguration. You can't really do anything with them that I can tell. If I try to uninstall, reinstall or anything I get a message like "This package contain plugin file. Use MP Installer to resitall it!" Apart from the grammatical and spelling errors, it is just funny because the Tab says MP Installer. So I thought I was using the MP Installer!!!!</p><p></p><p>4. Provide some simple and clear documentation on creating an MPI file for skins or plugins. Ideally a help file with the Create Extensions section. And add a place for documentation files! </p><p></p><p>5. Possibly separate sections under Create Extension for Skins vs Plugins. The Skins one should be pretty easy in comparison. You could even provide a basic template for creating skin extensions since that should be pretty consistent. And ask some developers to test it. If it takes longer than 5-10 minutes forget it.</p><p></p><p>6. I don't know if MPI does this now, but MPI should be able to check what version of MP a user is using, and inform them if the plugin or skin is not supported for this version. THEN users will refuse to use anything but the MPI!!! We are all tired of loading incompatible versions of skins and plugins (which sometimes don't even tell you which version of MP they support)</p><p></p><p>As far as getting the developers to use the installer, I hope they will let you know why they don't. But also, you have to give developers a good reason to use MPI. If it cannot be part of the main configuration, then isn't it easier for users to use a standard .exe install, which is what they are used to? How do you answer that? I mean what are the advantages of using MPI? I am sure there are lots, but do the developers know what they are?</p><p></p><p>I hope these suggestions are helpful. I mean them as support and encouragement for your efforts. As a user, I welcome and applaud all your attempts to make MP installation and configuration easier!</p><p></p><p><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p></blockquote><p></p>
[QUOTE="Dadeo, post: 359947, member: 27204"] Yes!!!! I am fully in support of some standard installer for plugins AND skins. When I first loaded MP (before MPI existed) I really did not think it was going to be a good program. At that time, even the main installation was not very good. And what I had to go through to figure out how to install plugins and skins. Well it just didn't look very professional and did not reflect the quality of MP (which is my favorite software EVER). The new Installation is MUCH better, but the plugins and skins... need I say more? I agree with Revs, the best option would be in the main application, but if not, then the MPI tab under Plugins should take you there directly (hopefully without exiting the main configuration! and return you to configuration when you are done or give you an option to exit) So here are my suggestions of what you can do in the near future: 1. Link MPI to main plugin (tab) AND skin configuration (I can't find any reference to MPI under Skin Configuration) 2. Call it something more user friendly than MPI, like Plugin Installation, Skin Installation (Extensions is becoming more widley used, so that might work!) 3. Have an option to check the repository for plugin/skin updates that match your current release of MP (I think the Check for Updates checks for updates to MPI? I'm not sure) 3. Get rid of the icons in the current MPI tab under Plugin Conifiguration. You can't really do anything with them that I can tell. If I try to uninstall, reinstall or anything I get a message like "This package contain plugin file. Use MP Installer to resitall it!" Apart from the grammatical and spelling errors, it is just funny because the Tab says MP Installer. So I thought I was using the MP Installer!!!! 4. Provide some simple and clear documentation on creating an MPI file for skins or plugins. Ideally a help file with the Create Extensions section. And add a place for documentation files! 5. Possibly separate sections under Create Extension for Skins vs Plugins. The Skins one should be pretty easy in comparison. You could even provide a basic template for creating skin extensions since that should be pretty consistent. And ask some developers to test it. If it takes longer than 5-10 minutes forget it. 6. I don't know if MPI does this now, but MPI should be able to check what version of MP a user is using, and inform them if the plugin or skin is not supported for this version. THEN users will refuse to use anything but the MPI!!! We are all tired of loading incompatible versions of skins and plugins (which sometimes don't even tell you which version of MP they support) As far as getting the developers to use the installer, I hope they will let you know why they don't. But also, you have to give developers a good reason to use MPI. If it cannot be part of the main configuration, then isn't it easier for users to use a standard .exe install, which is what they are used to? How do you answer that? I mean what are the advantages of using MPI? I am sure there are lots, but do the developers know what they are? I hope these suggestions are helpful. I mean them as support and encouragement for your efforts. As a user, I welcome and applaud all your attempts to make MP installation and configuration easier! :thx: [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
The future of MPI - we need your opinion!
Contact us
RSS
Top
Bottom