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)
Extension Installer V2
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="dukus" data-source="post: 518283" data-attributes="member: 18021"><p>How i see the current extension installer not really used. The some of problems with it, this interface not really help the devs, no possibility customize the setup, depend on a online repository which not exist, impossible to use with MP2 and many more.. So i decide to rewrite from zero. </p><p></p><p>The base functionality of a installer is to copy a file to a specified location on user system. The new installer based on "providers", (maybe not the right name), with this providers it is easy to extend the system.</p><p style="margin-left: 20px"></p> <ul style="margin-left: 20px"> <li data-xf-list-type="ul"><strong>InstallerType</strong> - This provide how the installer handle the files. Like "CopyFile" copy the included file to the specified location or "RegisterFont" register the included font in system.</li> <li data-xf-list-type="ul"><strong>PathProvider</strong> - This provider transform path templates in real path in user system.</li> <li data-xf-list-type="ul"><strong>SectionPanel</strong> - This are forms included in install wizard, like "Welcome Screen" or "Component Selector"</li> <li data-xf-list-type="ul"><strong>ActionType</strong> - This are actions attached to the panels like ("Install files", "Kill process") </li> </ul><p></p><p>For updates the extension dev should provide a url were is a version descriptor xml file. This file may be hosted in google code, or in Mediaportal server. The available extensions will be browsed on mediaportal site. The installer manage (UnInstall, Update) only the installed extension. Every extension have a unique GUID so can be identified after name change too. </p><p></p><p>The installer use groups to made install option. If a group is checked the all files belong to this group will be installed.</p><p>The install wizard have sections, every section visibility may depend on a group check. </p><p>Try to make the installer with same functionality like a NSIS or a MSI installer, but with a dev friendly user interface to make this install package.</p><p></p><p>The installer have 3 parts : </p><p>MpeMaker - utility to create extension packages (this should used by the devs) and </p><p>MpeInstaller - utility to manage the extensions (Install, UnInstall)</p><p>MPEIPlugin - window plugin to manage extensions </p><p></p><p>A small To-Do list :</p><ul> <li data-xf-list-type="ul"> Installer type<ul> <li data-xf-list-type="ul">Font installer - <strong>done</strong></li> <li data-xf-list-type="ul">Generic Skin installer - <strong>done</strong></li> </ul></li> <li data-xf-list-type="ul">Actions<ul> <li data-xf-list-type="ul">Shortcut creation on a specified location <strong>done</strong> </li> <li data-xf-list-type="ul">Included package installer <strong>done</strong> </li> <li data-xf-list-type="ul">Register DirectShow filter</li> <li data-xf-list-type="ul">Add registry key to windows registry</li> <li data-xf-list-type="ul">Lunch separated application - <strong>done</strong></li> <li data-xf-list-type="ul">Add settings to MP</li> <li data-xf-list-type="ul">Create folder - <strong>done</strong></li> <li data-xf-list-type="ul">Kill running task - <strong>done</strong></li> <li data-xf-list-type="ul">Clear skin cache - <strong>done</strong></li> <li data-xf-list-type="ul">Show message box - <strong>done</strong></li> </ul></li> <li data-xf-list-type="ul">Wizard sections<ul> <li data-xf-list-type="ul">Wizard section with radio buttons</li> <li data-xf-list-type="ul">Wizard section with check boxes - <strong>done</strong></li> <li data-xf-list-type="ul">More customizable Wizard sections (Title, log, etc) - <strong>done</strong></li> <li data-xf-list-type="ul">Script capabilities CSScriptLibrary - <strong>done</strong></li> </ul></li> <li data-xf-list-type="ul">Misc<ul> <li data-xf-list-type="ul">Version checking - <strong>done</strong></li> <li data-xf-list-type="ul">Compatibility with Vista and W7 - <strong>done</strong></li> <li data-xf-list-type="ul">Support for tv server plugins - <strong>done</strong></li> <li data-xf-list-type="ul">Uninstall - <strong>done</strong></li> <li data-xf-list-type="ul">Update checking - <strong>done</strong></li> <li data-xf-list-type="ul">Plugin for The Installer</li> <li data-xf-list-type="ul">List for installed extensions <strong>done</strong></li> </ul></li> </ul><p></p><p></p><p>Links to older discussion :</p><ul> <li data-xf-list-type="ul"><a href="https://forum.team-mediaportal.com/skins-plugins-installer-mpei-212/future-mpi-we-need-your-opinion-52583/" target="_blank">https://forum.team-mediaportal.com/skins-plugins-installer-mpei-212/future-mpi-we-need-your-opinion-52583/</a></li> <li data-xf-list-type="ul"></li> </ul><p></p><p>This installer file format isn't compatible with older mpi format</p><p>For testing use latest SVN. To make a extension Use MPEMaker.exe and for install it use MPEInstaller.exe</p><p></p><p>So i need feedback especially from plugin devs and from skinners.</p></blockquote><p></p>
[QUOTE="dukus, post: 518283, member: 18021"] How i see the current extension installer not really used. The some of problems with it, this interface not really help the devs, no possibility customize the setup, depend on a online repository which not exist, impossible to use with MP2 and many more.. So i decide to rewrite from zero. The base functionality of a installer is to copy a file to a specified location on user system. The new installer based on "providers", (maybe not the right name), with this providers it is easy to extend the system. [INDENT] [LIST] [*][B]InstallerType[/B] - This provide how the installer handle the files. Like "CopyFile" copy the included file to the specified location or "RegisterFont" register the included font in system. [*][B]PathProvider[/B] - This provider transform path templates in real path in user system. [*][B]SectionPanel[/B] - This are forms included in install wizard, like "Welcome Screen" or "Component Selector" [*][B]ActionType[/B] - This are actions attached to the panels like ("Install files", "Kill process") [/LIST] [/INDENT] For updates the extension dev should provide a url were is a version descriptor xml file. This file may be hosted in google code, or in Mediaportal server. The available extensions will be browsed on mediaportal site. The installer manage (UnInstall, Update) only the installed extension. Every extension have a unique GUID so can be identified after name change too. The installer use groups to made install option. If a group is checked the all files belong to this group will be installed. The install wizard have sections, every section visibility may depend on a group check. Try to make the installer with same functionality like a NSIS or a MSI installer, but with a dev friendly user interface to make this install package. The installer have 3 parts : MpeMaker - utility to create extension packages (this should used by the devs) and MpeInstaller - utility to manage the extensions (Install, UnInstall) MPEIPlugin - window plugin to manage extensions A small To-Do list : [LIST] [*] Installer type [LIST] [*]Font installer - [B]done[/B] [*]Generic Skin installer - [B]done[/B] [/LIST] [*]Actions [LIST] [*]Shortcut creation on a specified location [B]done[/B] [*]Included package installer [B]done[/B] [*]Register DirectShow filter [*]Add registry key to windows registry [*]Lunch separated application - [B]done[/B] [*]Add settings to MP [*]Create folder - [B]done[/B] [*]Kill running task - [B]done[/B] [*]Clear skin cache - [B]done[/B] [*]Show message box - [B]done[/B] [/LIST] [*]Wizard sections [LIST] [*]Wizard section with radio buttons [*]Wizard section with check boxes - [B]done[/B] [*]More customizable Wizard sections (Title, log, etc) - [B]done[/B] [*]Script capabilities CSScriptLibrary - [B]done[/B] [/LIST] [*]Misc [LIST] [*]Version checking - [B]done[/B] [*]Compatibility with Vista and W7 - [B]done[/B] [*]Support for tv server plugins - [B]done[/B] [*]Uninstall - [B]done[/B] [*]Update checking - [B]done[/B] [*]Plugin for The Installer [*]List for installed extensions [B]done[/B] [/LIST] [/LIST] Links to older discussion : [LIST] [*][URL="https://forum.team-mediaportal.com/skins-plugins-installer-mpei-212/future-mpi-we-need-your-opinion-52583/"]https://forum.team-mediaportal.com/skins-plugins-installer-mpei-212/future-mpi-we-need-your-opinion-52583/[/URL] [*] [/LIST] This installer file format isn't compatible with older mpi format For testing use latest SVN. To make a extension Use MPEMaker.exe and for install it use MPEInstaller.exe So i need feedback especially from plugin devs and from skinners. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
Extension Installer V2
Contact us
RSS
Top
Bottom
