SkinUpdater (Plugin Mockup) (1 Viewer)

[Edalex]

Hi guys!
Input data:
- it is hard to download full mpei package for skin updates
- StreamedMP patch system requires c# knowing for skinner
- MPEM is proposing updates but is far from end
So I decided to make skin updater system based on svn (and maybe git in future).
Tested on Frames by @Lbr_Lion and Black Glass Nova by @Tgx
Just need to put SkinVersion.xml file in skin folder with svn revision you think your skin have now and link inside
UPD: Autoupdate is not working for now. Need to decide if it is needed at all

 

[catavolt]

THX - will try out

 

[Edalex]

Unfortunately, my favourite skin's (DefaultWide) repo is not supported as I didn't choose git library to use with plugin

 

[azzuro]

i think missing one thing,
so git repo as you say
and missing MP version !!!
Skinners have always the same repo for all MP version ( update)
if user use this plugins with MP1.3 your plugin can (should) only update the skin to the last commit for your MP version .
so for that skinner need to add skinupdate.xml in repo

like node :

<update>
<MP>1.3.100.0</MP>  <!-- MP 1.4 RC -->
<Commit>SHA-1 code</Commit> <!-- last commit for version -->
</update>
 
<update>
<MP>1.4.0.0</MP>  <!-- MP 1.4 Final -->
(No <Commit> node because dev is not stopped for this version of MP)
</update>

and you can also add an "Force Update" own risk and peril

 

[azzuro]

second thing : never hardcoded string

 

[Edalex]

Sorry @azzuro I can hardly understand you
Skinners always have separate repos/branches fro every mp version so this plugin will suilt best for minor updates. did you mean the same?
Also I thought about general skin loading. This GUIWindow method https://github.com/MediaPortal/MediaPortal-1/blob/master/mediaportal/Core/guilib/GUIWindow.cs#L458 is responsible for this. It will be cool if mp could download needed skin file on-the-fly if it can't find needed local file of use i.e. file from defaultwide skin.

second thing : never hardcoded string

Well, it is called mockup and it shouldn't even work. I just wanted to raise a discussion.

 

[azzuro]

Skinners always have separate repos/branches fro every mp version so this plugin will suilt best for minor updates. did you mean the same?

i don't know if all skinners have dedicated repo for each version of MP, but if not, we need have my xml proposal, i think more easy for skinners
because all Git repo ( maybe svn) can related commit to an TAG,
example MP repo, MP1.4 tag is related to "SHA-1 XYZ" and if you want compil the Final MP 1.4 you need compil the commit set in TAG

Well, it is called mockup and it shouldn't even work. I just wanted to raise a discussion.

no problem

i like you plugins : because
- solution for have only one plugins fo update skin
- can update all skin for plugins

but should be added to MPEM, because skinner need to publish MPEI files for 1st installation

 

[Edalex]

Still can't get this idea from my head. And honestly I don't want to deal with svn and git tools to perform updates.
What about little tool placed in skin folder which could generate list of files in folder. And plugin will grab it and decide what file needed for download.

 

[catavolt]

Well, the tool could read the file changed date and produce an update mpei for the changed files only.

 

[Edalex]

mpei is a zip package and since users can have different skin versions locally you'll need to store tons of [ackage for each case. So i'm still for downloading individual files by direct links.