The future of MPI - we need your opinion! (1 Viewer)

[tourettes]

Just tested back home in my Vista Ult. box, and fonts are not copied to C:\Windows\Fonts as they are in Windows XP when using the MPI. That's a showstopper

Make sure that you have rights to write into that folder with the user you are launching the MPI installation.

I think the ideal solution would be for the UAC Security Prompt to pop up and ask the user for temporary admin permissions to install anything requiring it.

Yes, that would be the correct way to handle it. (if its the permission issue).

 

[x4mer]

Could MPI be made to take care of this?

https://forum.team-mediaportal.com/...e-file-parsing-avoid-plugin-reinstalls-48702/

 

[infinite.loop]

I had problems with the MPI package not installing the fonts under Vista, and installing corrupted fonts under XP. Could one of the devs confirm this problem?

I have just noticed that under vista "drap and drop" (or plain copy) fonts into "Windows/fonts" is not working (UAC off + Admin account).
VISTA throws an error message containing some chinese symbols

Only way to install fonts on VISTA seems to be select fonts -> rleft click -> install

But there has to be a other solution to do "the same" in code of MPI. I am sure dukus will it.

 

[framug]

There is a ClearSkinCache option for deleting skins cache.
It could also be great to have a ClearConfigPlugin for deleting plugin xml file, when plugin has many changes which implies no descending compatibility.

 

[ltfearme]

Can someone confirm the ClearSkinCache functionality, last time I checked it didnt work but it could of been fixed now.

https://forum.team-mediaportal.com/...ar-skin-cache-property-not-working-mpi-47089/

 

[p0wah]

offtopic...

 

[Eyep0p]

sorry if someone said this already...

it would be cool to install plugins and skins from within mediaportal! (as already seen in meedio)
ok maybe it can be a problem because many plugins and skins need special configuration. (that btw could also be a difficult thing for the end-user)

 

[moiristo]

Just my 2 cents:

1) Documentation: What do all features mean? How do I release an update of the plugin? I have really no clue how the latter should be done, while I'd really like to use it!
2) Testing: Please write tests! When I was still using MPI, I often got feedback of people that were missing skin files after using MPI. You need to be sure that you've covered all corner cases to guarantee its stability.

 

[ibmonkey]

would it be possible to have the option to allow a plugin to automatically update itself if a new valid version is released?

i'm thinking in particular about an mpi that installs TV channel logos, if there were changes to some TV channels and the mpi was updated in the repository, could the mpi installer pick up on the update and install the mpi automatically?

 

[1gkar]

I hope I am not misinterpreting some aspects of this thread, but there seems to be some anger out there about how MP going to be coded in the future.

As someone who is only moderately PC literate, my only experience with using MPI was dismal. I won't state the plugin, but it was one I want to use -& still would. But it caused major bugs on my MP install (MPRC4) -ie, I lost ALL plugin icons within MP>config utility. No, I didn't bother with the bug-reports & all that, as I all I want is something that works. Sorry if that flys against opensource protocol: but too bad. If something doesn't work, I simply reimage & carry on. I don't have the time to read through some 8-15+ pages of forums posts for a possible answer. I just Ghost back & continue on with life.

My point: the documentation DOES need accurate representation of the plugin's capabilities, & it's limitations: in plain English. Also, I have never had any real issues with the system that stands at present: ie. using *.msi & manual installs of the various *.dll & other files. The plugin & skins devs do a great job, on the whole, at present & should be applauded for their efforts, especially in the continual improvements of their products. To force them to learn a whole new area of development, which will take them away from their area of concentration, & in a lot of cases, put their plugins' development back, may, in time be harmful to the entity that is Mediaportal. Again, I speak from a standpoint of one who has no real understanding of programming & coding. But I know what I need in a programme, & to date, Mp more than fullfils my requirements.

I have used MP for about two years, now & one of the reasons I started using it, was it's relative simplicity compared to other similar programmes on the market. Considering its status compared to commercial programmes, I believe it is THE BEST HTPC front-end option in the marketplace, & judging from the amount of MP donator badges I see on the forums, I'm not the only one to think that. Please, don't f*&^ it up for the sake of perceived improvements that may never be.