Extension Installer V2 (1 Viewer)

[Dadeo]

OMG Dukus, I barely got the words out of my mouth and you have already done the single line display. Yes, those new files (zip) worked like a charm. I still get the exception error if I cancel a download though.

Sure, it is not really pretty yet, but imo it is very functional! Also no more flashing when I select different release notes either! Yahoo!

Now we just have to get all our developers to do some nice icons like some of the extensions have so we don't end up with too many brown boxes I don't see why they don't use the same icons used in MP Config and I have never understood why we can't have hover images that match.

I still think you could make the size of the notes smaller and scrollable, but that is certainly only a preference or wish not a requirement. It is hard to know how it will display on diff screen sizes and I am using my computer screen at 1280x1024 atm to view and for the screen shots.

For anyone who wants to see the new display Dukus created I attached a screen shot. If Catavolt is around he will notice aMPed is highlighted

 

[mackey]

Hi Dukus,

How can I delete the latter of the two instances of MyLyrics? As you might remember, a previous version of MPEI2 made a particular project file crash which in the end led to two instances.
cheers

 

[catavolt]

AW: Extension Installer V2

Hi Dukus, big for the new version. It is much more readable as the actual version of MP RC1. Screenshot attached - and Dadeo, guess what is highlighted?

 

[dukus]

mackey, you should edit manually the MyLyrics_MPE1_BETA.xml file, there is a section with 9c5a23fa-19b4-4867-bf25-176e79753869 id, you should delete that section <PackageClass>....</PackageClass>.

For online support, it is indicated to name the .mpe1 files with separated name for every version, in this way the can install a older version to not only the latest....

Another thing, more easy to update the update.xml file if is linked from SVN, and the .mpe1 should stored in download area were it is sown the download count for every version

 

[MrCrabs]

Dukus: Ok, it says "known extensions" but somehow I always thought that it meant all known extension that are available for MPEI....

And to what dadeo said: Of yourse I'd like MPEI to only show all extensions that are compatible with my system, so first with MP version, next maybe the skin might also deliver a list of all right now supportet extensions, and then I just might select and install one and all is fine.

Just take as a suggestion for further developement. I don't know if that is possible at all. But it would be pretty cool.

 

[SpudR]

I know things are progressing with this, but how about showing ALL the plugins detected within MP and highlighting the ones which cannot be installed with the MPEI with some icon or shading?
For example - I had already installed OnlineVideos v0.17, but the MPEI didn't detect it. I have now installed through MPEI and it's there in 'installed plugins' now and updatable.

Also how about adding a tick box to the plugins/skins and selecting the ones you wish to install - and a 'Go' button.
simple installation of multiple plugins...

This is truly fab even at this early stage

 

[Dadeo]

Re: AW: Extension Installer V2

Dadeo, guess what is highlighted?

I got so excited I updated my online update info, right away, but PureVision did not appear

@Mr. Crabs -

next maybe the skin might also deliver a list of all right now supportet extensions, and then I just might select and install one and all is fine.

That is a really interesting idea! As a skinner, it drives me crazy trying to keep a list updated of exactly which plugins and versions are supported by aMPed. So now you got me thinking! Certainly there could be a text list of supported plugins or a link to such, but that is only slightly better than what we have now.

Can you think of any way this might be easy to add to MPEI Dukus? Wouldn't it be great if MPEI could cross reference all the skins and plugins - you pick a skin and can select an option to see all the plugins it supports (i.e. the ones compatible with MPEI ). You select a plugin and can press an option to see all the MPEI skins that support it! Could this be done in update files somehow or some other way?

I know I could add a version tag within the xml file(s) for a plugin. I already do that in aMPed for some of the different options available and our aMpedConfig program uses those. But my sense is that would not be the best way for MPEI, and it is almost as tedious as keeping the list of supported plugins updated.

Any ideas Catavolt?

 

[dukus]

For plugin-skin compatibility is the generic skin, which should solve the "not working" problem

For plugin-plugin, plugin-mp compatibility, it is possible to define in mpei package one or more dependency

For a installed extension if one ore more dependency not found a red triangle will be displayed, when install a new extension the user will be notified if a dependency not found (configurable in mpei if the installation should continue or not). In nest version i will add same thing (red triangle) for know extensions and a checkbox to hide this extensions

 

[mackey]

mackey, you should edit manually the MyLyrics_MPE1_BETA.xml file, there is a section with 9c5a23fa-19b4-4867-bf25-176e79753869 id, you should delete that section <PackageClass>....</PackageClass>.

There were six <PackageClass> sections. I have deleted three of them and left 1.4.2.0-1.4.4.0 for the version that I would like to keep. That didn't change anything though.

 

[dukus]

For testing you should delete (rename it) the local file [AppData]\MediaPortal\Installer\V2\KnownExtensions.xml