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="Bagal" data-source="post: 360276" data-attributes="member: 27764"><p>I personally think that the browsing of plugins and skins in the repository should be in the Configuration app rather than a separate application, I appreciate that actually installing them via the Config won't work due to the architecture of MP but once the plugin or skin is downloaded the Config should be closed, the extension installed and then the Config restarted, something like the following workflow:</p><ul> <li data-xf-list-type="ul">User chooses extension manager/plugin installer section in Config app</li> <li data-xf-list-type="ul">User browses list of extensions and chooses one to install</li> <li data-xf-list-type="ul">Extension downloaded</li> <li data-xf-list-type="ul">Config quits</li> <li data-xf-list-type="ul">Extension installed</li> <li data-xf-list-type="ul">Config restarts</li> <li data-xf-list-type="ul">Extension config shown if appropriate</li> </ul><p>This method would also for the most part work within MP itself:</p><ul> <li data-xf-list-type="ul">User browses list of extensions and chooses one to install</li> <li data-xf-list-type="ul">Extension downloaded</li> <li data-xf-list-type="ul">MP quits</li> <li data-xf-list-type="ul">Extension installed</li> <li data-xf-list-type="ul">MP restarts</li> </ul><p>For extensions that require lots of configuration it wouldn't be appropriate to restart MP, so you could perhaps start the Configuration instead, options like this could be set within the MPI itself by the extension developer.</p><p></p><p>Bagal.</p></blockquote><p></p>
[QUOTE="Bagal, post: 360276, member: 27764"] I personally think that the browsing of plugins and skins in the repository should be in the Configuration app rather than a separate application, I appreciate that actually installing them via the Config won't work due to the architecture of MP but once the plugin or skin is downloaded the Config should be closed, the extension installed and then the Config restarted, something like the following workflow: [LIST] [*]User chooses extension manager/plugin installer section in Config app [*]User browses list of extensions and chooses one to install [*]Extension downloaded [*]Config quits [*]Extension installed [*]Config restarts [*]Extension config shown if appropriate [/LIST] This method would also for the most part work within MP itself: [LIST] [*]User browses list of extensions and chooses one to install [*]Extension downloaded [*]MP quits [*]Extension installed [*]MP restarts [/LIST] For extensions that require lots of configuration it wouldn't be appropriate to restart MP, so you could perhaps start the Configuration instead, options like this could be set within the MPI itself by the extension developer. Bagal. [/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