Need some change in the MP ISetupForm for webinterface (1 Viewer)

[pitie]

Yeah, some things are not easy to explain and can easily get complicated. Especially we're both not native english speakers. But as long as one of you understands what I'm talking about, I'm happy with it. :wink:
sure

Yes, that's one of the things i tried to explain. So one possibilty would be a base package and some update packages. An xml (or the db) on the server keeps track of them and the update application decides what is necessary for download. It's all a bit complicated, so I'm open for any suggestions at that point. But I guess you (and guilhem) got the idea what I'm driving at.
Ok all version in the DB as an unique ID so if I have version 1.0 of a plug where unique id = 234 and an update for version 1.1 is out with unique id 239, it will download only the 234_to_239.mpi file
If i have a plugin v1.0 (uniqueid=234) and an new version 1.1(uniqueid = 239) is out but i don't take it and now a new one 1.2 is out(uniqueid =245) it will download complet package 245.mpi

I think it is enought ? or should he must download 234_to_239.mpi and next 239_to_245.mpi ?
I dont think it is usefull because of space on server will be used a lot !!!
I think only new version and last version to new update is enought...

Do you agree?

 

[mPod]

Ok all version in the DB as an unique ID so if I have version 1.0 of a plug where unique id = 234 and an update for version 1.1 is out with unique id 239, it will download only the 234_to_239.mpi file
If i have a plugin v1.0 (uniqueid=234) and an new version 1.1(uniqueid = 239) is out but i don't take it and now a new one 1.2 is out(uniqueid =245) it will download complet package 245.mpi

I think it is enought ? or should he must download 234_to_239.mpi and next 239_to_245.mpi ?
I dont think it is usefull because of space on server will be used a lot !!!
I think only new version and last version to new update is enought...

Do you agree?

Yes, I'm very happy with that solution. Nevertheless it would be very cool if you build the system the way that just in case we wanna have more detailed update steps, we can easily implement it without breaking the structure you just described. Future proof in this case as well, if possible.
But as said, your suggestion is a very good way in between, cause we have to balance traffic and server space for now, of course. Very good idea.

 

[mPod]

Btw, I didn't mention it before, but thanks for all your efforts so far! Me and the rest of the team are really looking forward to that promising product at the end.

Looks like we have some very cool and productive discussions going on here. Let's keep it going! :lol:

 

[guilhem]

One thing we didn't talk about yet...
Does your system also contain a section in MediaPortal where all downloadable plugins are categorized and listed? This gives us great opportunities, cause we only need to have basic stuff in our official MediaPortal distribution then.
The user sits on the couch and chooses with his remote control what plugin he wants to install. Do you know Linux' YAST? That's one example of a list with installable modules (in our case plugins or skins or...).
So the user does not have to use a web browser to download the initial version of plugins and can do all integrated in MP's GUI with the press of his thumb.

I don't know Linux Yast but yes we have think at this solution.

Just a little overview to resum. We think all the plugin system in 4 step.

- the plugin package (MPI) : a zip file which contains all the plugin files and the way to instal or uninstall

- the plugin web server (PWS): a db of all plugin and version. I think an interface on diferent sites (official, french,...) by rss maybe.

- the MPI maker for easily make MPI file and interface with the plugin web server

- the plugin web installer (PWI) : first it's a plugin but we think it will be include in MP configuration mode ( but not in 0.2 ): so the user can easily download and install plugin.

It's so beautiful, isn't it ? :lol:

But one things after the other, we just start...

 

[mPod]

Sounds great so far. Important is that the structure of the installer/the packages is fixed and doesn't have to be changed in the future. All other stuff is cosmetic and can be done one after the other, of course. And all after 0.2.

Some questions, our Admin still doesn't know what you need on the server? Am I right that you need PHP, MySQL and an Apache server? What else do you need?

What do you need RSS for and how do you want to create RSS feeds? With PHP, I guess?