auto-update

[dottore]

it would be nice to have an auto-update-function in gbpvr. not just for the main program but specially for the plugins. the my-series is updated very often for example.

the problem is, that the skins must be updated too, when there are skin-changes in the plugins....i don't know, how this problem could be solved. any ideas?

since this auto-update-function needs connection to the internet the installation of plugins could be made easier: just check the plugin you need and the configuration-program will perform a download of the plugin.

[reven]

i suggest something else, well wish, cause its never going to happen (well probably not). if you ever seen avalaunchx (most probably havent, its a xbox dashboard replacement), it has this option to check for updates/skins/whatever and you can decide if you want to download them and then it auto installs, gbpvr could display a news ticker on the main menu, and say "my videos updated" then goto "settings" (my god this is a big wish) click downloads, which only displays the new items and you can download it and install it, this would work for gbpvrs core aswell (of course it would check if a recording is in progress or about to start before it is installed).

now thats my wish, so sub do it! (just kidding, kinda ).

[dottore]

good idea. probably, this auto-update-function could be implemented as a plugin for the beginning....a plugin, checking for the date of the files on the wiki. of course, this would only work, if the filenames don't change.

the plugin could also point to some links (this could also include gb-pvr-core) which lead to the proper files or something like that.

the plugin-developers and sub would only have to provide their files and add them to the "list of links", maybe with a description to which folder the files should be copied, e.g.: gbpvr-core --> gbpvr-directory, myVideos --> plugin-directory and skin-directory, blueMCE2 --> skin-directory and so on....

[reven]

yeah the auto update is a more likely wish, and in the short term a really good idea, my idea is something far down the line, just an idea "this would be so cool" but "my god this would be a pain in the arse to do". just make gbpvr poll gbpvr.com every few hours (or something) to see if an update is available, if it is start downloading it, and install.

mediaportal just did this, i assume this is why the wish was made (its a little buggy thou, didnt update for me).

[dottore]

i think, the easiest way would be to make a plugin (probably including a panel for the home menu :-)) which looks for updates every time it is activated. looking for updates means to parse a xml-file or a simple webpage with the information on the updates.

would mean, that every time, someone updates a plugin or a skin, one would have to update this xml-file or simple webpage.

this leads to another idea: the webpage, called from the update-plugin could be created dynamically every time the plugin calls the page. the webpage parses the wiki and/or gbpvr.com and displays the information....

wouldn't be THAT complicated. in the future the plugin could even perform some update-action, depending on the plugin (e.g. delete old db-files before installing new ones) or perform a silent install of gbpvr when there are core-updates.

[reven]

errr i dont know, i know very little about internet programming, doing a paper on it this semester, maybe ill learn how to do this

[dottore]

i'm doing this for a few years now, i'll try a bit...

[reven]

yeah, you'd probably have way more luck than me just talk to a lot of plugin developers, sub, probably blader_se if you doing the wiki thing. ill add support for this in all my plugins/skins if you get it going.

[dottore]

i'll try following: i will parse the wiki and display the plugins and skins in a list. a plugin (done by myself) must compare the date between local and remote files/plugins, then download the files, unpack them and install them depending on the included files or folders.

not too hard, but a lot of work ;-) i'll do my very best. doing it this way i do not need any help or changes from the plugin-developers which makes things more handy. a plugin-developer would just have to add the plugin to the wiki. when this is working, i'll try to optimize the whole thing, maybe then i need some help...

[reven]

i dont think you need to parse the page, we can maintain a file you can simple download and get the info that way (errors can occur with parsing), maybe a online database? mysql or something, when the wiki is updated, blader can add more info to the upload part, like build number/version, record the date,then you can just poll the database. if the wiki cant be changed, im sure everyone wont mind going to another page and reentering all the info. that way it would be far more reliable.

might have to upload two different versions thou, since sometimes if i update something only the dll has been changed, or just the dll and the skin.xml (no need to download every other file), but this then means more storage space, but less bandwidth is used.