Re: [misterhouse-users] Upgrading Misterhouse

[Joel M. <joel@ButtonsByGina.com>]

I was playing with something similar to this.  I don't like the idea of
actually updating the software without any user intervention, but I wrote a
script for monitoring the download page for the current version, notifying
you if the current version is different than the one you are running, and
giving the option to download the new version.  There's a bunch of stuff
hardcoded into it that I wanted to put in the INI file before sending it
out, but it does work (with my limited testing).  Let me know if you want
and I'll send you a copy.

Joel

----- Original Message -----
From: "John Edmonds" <pe...@kc...>
To: <mis...@li...>
Sent: Thursday, December 06, 2001 8:35 AM
Subject: [misterhouse-users] Upgrading Misterhouse


> I was thinking on the way to work yesterday (I know, that was the first
> mistake...)
>
> Would it be possible to have MH self-update?
>
> I have no idea if this can be done, or what kind of implications it would
> have.  It would be great if the "core" components would check (either
> automatically or activating a button widget from the interface) for a
newer
> version and download/install the files.
>
> The "add-on" components could then be like subscriptions and check for
> updates too.  (Possibly having the modules in the MH.ini that it would
check
> for updates or building into the "add-ons" the update routines.)  This
could
> possibly work in conjunction with SourceForge
>
> I realize that some "add-ons" and "core" components have device/home
> specific information, so they would require parameters in the MH.ini file
or
> some other file that could be individually localized.
>
> Just a thought...
>
> --John Edmonds
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365
>