Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 360969" data-attributes="member: 52082">I think better documentation for the whole MPI system would be the first step in the right direction. As several people have mentioned already it is a pain in the ass to build a new MPI and the process is not documented well at all.One feature I would like to have though, is a way to conditionally install certain components based on conditions on the install machine. For example, Moving Pictures has a generic skin that can be used with any MediaPortal skin. It would be nice to be able to automatically copy the appropriate version of the generic skin (16x9 or 4x3) to all skin folders that do not already have a movingpictures.xml file. I could not do this right now with the MPI system, but it would not be too difficult with an MSI or InstallShield.I think update notification with automatic download and install would be an awesome feature but that is a big feature. I think I'd almost rather see everything already in there polished off first before you all move onto big new features. But of all the big features mentioned I think this is one of the most important.And I know InfinityLoop (or maybe one of the other devs?) said that because of the existing architecture of the config, it would be impossible to integrate the plug-in/skin installer into the config screen. But I have to say, this is very very important for usability. The user should not have two separate applications to configure MediaPortal. In fact I think this would be a good oportunity to revamp the skin and plugin sections of the config. The user should be able to browse available skins right from the skin selection tab. If he selects one that is not yet downloaded it should automatically be pulled down and installed. No fuss no muss.</blockquote>

[QUOTE="fforde, post: 360969, member: 52082"] I think better documentation for the whole MPI system would be the first step in the right direction. As several people have mentioned already it is a pain in the ass to build a new MPI and the process is not documented well at all. One feature I would like to have though, is a way to conditionally install certain components based on conditions on the install machine. For example, Moving Pictures has a generic skin that can be used with any MediaPortal skin. It would be nice to be able to automatically copy the appropriate version of the generic skin (16x9 or 4x3) to all skin folders that do not already have a movingpictures.xml file. I could not do this right now with the MPI system, but it would not be too difficult with an MSI or InstallShield. I think update notification with automatic download and install would be an awesome feature but that is a big feature. I think I'd almost rather see everything already in there polished off first before you all move onto big new features. But of all the big features mentioned I think this is one of the most important. And I know InfinityLoop (or maybe one of the other devs?) said that because of the existing architecture of the config, it would be impossible to integrate the plug-in/skin installer into the config screen. But I have to say, this is very very important for usability. The user should not have two separate applications to configure MediaPortal. In fact I think this would be a good oportunity to revamp the skin and plugin sections of the config. The user should be able to browse available skins right from the skin selection tab. If he selects one that is not yet downloaded it should automatically be pulled down and installed. No fuss no muss. [/QUOTE]

Verification