Wednesday, 15. November 2006, 17:30:17
EDIT: I've moved hosting back to MediaMax, though it shouldn't matter as you see in the installer in my other blog post.
I'm thinking that with posting the programs on this blog for my filterset, it would be possible to set up an autoupdater (or really from any HTTP file space). The design could be figured out in a week or so and likely up and running in another week. The issue of course is that
a) I don't update the filterset all that often
b) does anyone want one
c) if people wanted this, how did they want it to work?
My thought is a scheduled task that runs once a week or so to check for updates. If found, it would download the updates, and uncompress them over the old files. If desired, I think some management, specifically by moving most of the lists back into the "system" lists and keeping the user lists + some file manipulation with caveats could allow saving user modifications of the blocklists.
The bigger issue I see is the filters themselves. I'm thinking of if there is an easy way to keep userfilters, and I really don't think there is. (Not to say there isn't a way, just not an easy one that I'm aware of.)
I'm thinking about scripting this in AutoIT, and compiling it as an executable that way so everyone doesn't have to have the language installed.
Anyway, feel free to comment, if there is an interest, I'll see about hacking it together.
Ok, well - here's a basic updater that will just do what happens now, it will download the new file and overwrite the old files.
#cs ----------------------------------------------------------------------------
AutoIt Version: 3.2.0.1
Author: jp10558
Version: 1.1.5
Script Function:
Check for updates of my Proxomitron filterset, and if there are updates, download and install them.
#ce ----------------------------------------------------------------------------
Dim $Version,$Auto,$Website,$answer,$Update
SplashTextOn("OperaMOD Proxomitron Filterset", "Checking for updates....", 250, 30, -1, -1, 0)
$Version = IniRead("version.ini","Version","version","0")
$Auto = IniRead("version.ini", "Version","Auto","1")
$Website = IniRead("version.ini","Version","site","0")
InetGet($Website, "update.ini", 1)
$Update = IniRead("update.ini", "Update", "Update", "NotFound")
If $Update = $Version Then
SplashOff()
MsgBox(0, "Proxomitron Updater", "There are no updates.")
ElseIf $Update > $Version then
If $Auto = 1 Then
_update()
Else
SplashOff()
$answer = MsgBox(4,"Update Available","Do you want to update to Version " & $Update & "?")
If $answer = 6 Then
_update()
Else
EndIf
EndIf
Else
EndIf
Func _update()
Local $Site
$Site = IniRead("C:\temp\update.ini", "Update", "Site", "NotFound")
SplashTextOn("OperaMOD Proxomitron Filterset", "Downloading updates....", 250, 30, -1, -1, 0)
InetGet($Site, "proxy.exe",1)
SplashOff()
If ProcessExists("Proxomitron.exe") Then
ProcessClose("Proxomitron.exe")
EndIf
SplashTextOn("OperaMOD Proxomitron Filterset", "Installing updates....", 250, 30, -1, -1, 0)
Runwait("proxy.exe","..\")
FileDelete("proxy.exe")
FileDelete("update.ini")
IniWrite("version.ini","Version","version",$Update)
Run("Proxomitron.exe")
SplashOff()
EndFunc
And here's an exe for that:
ProxUpdate.exePlace that and this ini file
version.iniin your proxomitron top directory. The directory does need to be named proxy like my zipped distribution is.
Anyway, it's very hackish, and I pulled a lot of code from other AutoIT scripts on their forums.
You just put a windows scheduled task to run that exe every X days, and it pulls down the new one and installs it if there. But it does overwrite the old stuff.
So, I hope to do a couple things.
1) Implement a [Settings] section of the ini with an AutoUpdate key, which when set to 1 will do what it would do right now, just go do it, otherwise it will leave a message box up that there is an update, and did you want it to get it.
2) Impliment a progressbar for the download/indicator there is an update and now it's getting it.
From there it kind of depends. If I have time, I'll start work on one of these paths:
Either
1) an installer for the proxomitron set + autoupdater and the schedule setup and an updater for the updater.or
2) Changing up the set to not use the User lists and then not replace them. Plus seeing about breaking out "user" sections of the blocklists and maintaining them over the update.
The second path has lots of issues, specifically checking that with User-Include-Exclude that no matches are in that AND in the Include-Exclude list. Also, that leads to trying to find a way to just update the filters that have changed/save user filters too. Which looks really difficult to me.
Looks like the first is done, I have another blogpost for the installer... It works with WinXP to install the updater and set a scheduled task to check for updates once a week. You can of course edit that as normal in XP. It's not exactly an installer for proxomitron, though you could just point it at a directory at the same level of where you want proxomitron installed and away it goes. When I get a chance I'll make it more of an installer for proxomitron as well as for just the updater.
Anyway, the above was the easy part. The rest of the programming is bound to be more difficult.
WIDGETIZE