Updater plugin discussion thread

[QQQ]

Not that important, but...:
When there is an plugin that contains other folders (e.g. smileyAdd (the docs-folder)) and I uncheck every file in this folder before installing the new version, updater creates the folder anyway.

[sje]

ok, posted 0.4.0.3 on the beta site - should not copy the zips to the plugins folder (will still redownload - i plan to add an option to get files from the archives folder if possible) and it should also not create those empty folders

[QQQ]

tested with old smiley-add version, docs-folder still is created. :(

[sje]

oops - think i know why. i have updated it again...sigh...hop it works this time

[QQQ]

yeah, working fine now, thx :)
But I just had another bug, two times. After downloading the window opened, where I can uncheck the files I don't want to install. But there were no files.
Restarting Miranda and updating again fixed it.

And could u add an option to always ask for the files I want to install, without having to check the option in the dialog everytime?

[sje]

i think that happens when it fails to download the archive. the miranda site is being very slow/not working here...might have something to do with it

[AlexL]

Hello.

I suggest to insert "VS_VERSION_INFO" field in the DLL of Updater plugin. I often check this field in order to understand version of some Updater DLL (located outside Miranda directory). Without this field I have to save the current Updater.dll in other place, exit Miranda, copy the file in interest into Miranda plugins directory, start Miranda again, see the file's version, exit Miranda, move the old file back into plugins directory, and restart Miranda. And all this in order to check version of some updater DLL file (old or new).

This is not only annoying thing. More of this, if you do it several times, ICQ and Yahoo servers will prevent you from login for 15 minutes because of too intensive login activity.

I think that all Windows DLL-s and executables should have such field filled. Currently this is relevant for all Miranda plugins.

Thank you.

[sje]

i plan to include version information when the resources have stabilised a little more.

that's because, unless you do some 'include magic' it's too easy to accidentally forget to update either the internal plugin version or the version in the resources - and having them mismatched is much worse than not having them, imo. but using the include trick, i find i have to manually edit the resource file each time i modify it with visual studio - either that or make the resource uneditable with the resource editor - and that's also an easy thing to forget to do. i'm using version VC6 (miranda standard) for updater and it does not allow for multiple resource files.

so, when I think the options pages are sufficiently stable, i'll include version information via the include trick - unless someone can tell me how to get around the problems above?

[QQQ]

btw, what about the plugin-list in Updater-Settings? Not all plugins are shown there. Whats special about the ones, that are shown?
Would be nice, if there only would be shown plugins that are supported by updater, but I know of some plugins in this list, that they don't support updater.

[sje]

i figured out the resource thing (using the MSN resources as a template) - so the windows version information will be in the next release

which plugins are listed but not supported? i can create an internal list of plugins that should not be listed. the onces listed have internal names that match the file listing - so updater is able to locate them. it's not able to tell if the archive it has not yet downloaded is compatible.