Need some change in the MP ISetupForm for webinterface (3 Viewers)

[pitie]

Hi

So for the webinterface and MPI (MP installer)

I need in the ISetupForm just a version info in integer.

to get ascendant compatibily by defaut put it on 0.

Thanks

 

[samuel337]

Er... I'm confused - could you please try explaining it again, in more detail if you can?

MPW (MP web-interface) does not have an ISetupForm interface; I'm assuming you mean the External Control Plugin II that MP uses, which will have a ISetupForm interface in the new version soon to be released. The ISetupForm interface however doesn't allow for version numbers - it is not designed to do that. If you want to track the version of MPW, the best way would be to use the version number on the ECP2Assembly.dll file.

What exactly are you trying to do? If you're using the web service, the web service allows you to get the version numbers of the ECP2 Plugin through that, which would be easier.

I don't know what you mean by MPI either? Are you referring to MediaPortal's installer or MPW's installer? Why do you need to know the version numbers of these? Most people delete these files after they have installed MP or MPW.

Sam

 

[pitie]

I am sorry i didn't expain it well...
The french team are working on a mediaportal setup for plugin (it includ an standalone exe for install/unistall/download plugin, a webservvice with a db with all plugin, a webinterface in MP for viewing , installing and updating pplugin and finaly a setup maker for dev.)

The main setup program (exe) is done but don't have version control because plugin don't have version property. So it is why I ask it.

If we have time we will do that but we hope you will do it

 

[samuel337]

I'm not sure if MPW can be distributed like that, because its setup process is a bit complex. I'd be interested to know what sort of functions are available for the dev during the setup process (MPW requires multiple external programs to be launched to configure it during setup, and also an external program to be launched if password protection is required. It is also not a true MP plugin - it has a new application that controls the server which runs independently of MP).

Anyway, from the sounds of what your doing, just use the ECP2Assembly.dll's version property.

MPW consists of multiple parts, and the version numbers are not identical - e.g. there's the PHP-code, the ECP2 Plugin, and MPW application. We have not decided on having a single version number yet - but if we do this, we'll let you know. Note that sometimes only the PHP-code is updated, while during other times, only the ECP2 Plugin is updated. This is probably very different to other MP plugins, so we have plans to have our own updating facility. But we have not finalised this yet, so if you need an answer now, just use the ECP2Assembly.dll's version property.

How are you getting the version property out of other plugins? Just getting the assembly version metadata, e.g.:
System.Reflection.AssemblyName.GetAssemblyName(MPWECP2Path).Version.ToString();
where MPWECP2Path = path to ECP2Assembly.dll?

Sam

 

[mPod]

As mentioned several times before, we're already working on an installer/updater/server system for MP (without rendering old already compiled plugins useless!). You might wanna upload your ideas/code to sourceforge, so we can have a look at what we can use of it. So that might save some double work & time and lets us finish work on it even earlier.

Looking forward to it, we'd be happy to see more such contributions! :wink:

FYI, it will come some time after 0.2 release, so anybody asking for a date or other details is just wasting his time. :roll:

 

[pitie]

I have contacted Baravian and Lordmessy.

Our project is next to ready.

I send you last week a mail but no reply

MPI dev start 1 month ago but stoped because lordmessy said that you was working on it but recently i ask where you are and said me that you was working for building v0.2 of MP.
So I have proposed to do it and reply that ok.

So you can stop it i think.

MP webserver and interface and installer will be out in some days...

 

[samuel337]

MP webserver and interface and installer will be out in some days...

Er... MP webserver and interface and installer for that is NOT coming out in the next few days as far as I know - LordMessi or Maschine, please advise me otherwise.

I just wanted to clear up any confusion if there is any.

Sam

 

[mPod]

Not sure if we're talking about the same thing.

Anyway, I didn't get any mail. But no problem. As said, when you're done, upload your stuff to sourceforge and we'll see what we can use. That's the way it always goes, as everyone knows.

But of course, if you're talking about something completely different (I get the impression, cause of Samuel's answers), just forget what I said. Happy coding!

FYI: DMAN's the project manager, not LordMessi nor Bavarian. Only he knows who the team devs are working on. So in doubt always contact DMAN. I don't have to tell you, but work on it started more than a month ago. :wink:
If you have anything to contribute, we'd be happy to incorporate your work. As said, this saves some work & time and can never harm. Joining forces is the way to go in Open Source.

Again: When done, upload the stuff as everyone does and we'll see.

 

[samuel337]

But of course, if you're talking about something completely different (I get the impression, cause of Samuel's answers), just forget what I said. Happy coding!

I'm confused too...

 

[pitie]

MPI (the exe standalone setup) is on the french CVS

The PHP server too

Ok for the not understand.

I retry to explain it better

This project is in 4 part.

1 PHP server with a db where all plugin/skin are puted, mpi file were hosted on it.
Your team will be the moderator (for approve plugins/skin)
Translator will get an access to translation
Dev will be able to upload there projects (with MPI maker)

A MP plugin allow user to install MP plugin/skin in MP (no config todo, no download todo). just have to select what they want and MPI is launched
MPI close MP and install it. At the end of the install, MPI launch configuration of the plugin/skin (with the ISetupForm) and it restart MP

the dev will have MPI maker for doing there mpi file. It allow him to create a zip file renamed in MPI, add file to extract, language to add in the strings.xml of MP, editing registry and ini file, installing dll, adding some function to an existing skin (for exemple adding automaticaly a button to skin bluetwo in the TV main page...) and all other.

and to finish the config of the plugin in MP will add button install/unistall and update button.

I hope my explain is understand ?