if this is not something that you could do easily we have to depend on the default settings.

I'll look into this. I'm a bit busy with work at the moment so it might take a few days. I'm starting to think unzipping files from a zipped build folder and file copying like BBB's script would be easier.

how the app works right now is you start it, it'll run on the background. check the server on scheduled basis to see if there is a new build available. if that is the case it'll download and install the new build.

one question i have is what options would you prefer for scheduling. right now all i have in mind is everyday at a set time. and of course you could always initiate a check update manually.

Definitely don't have the default downloading daily as I dont think we can scale without funding. e.g. 1000 users updating daily is very roughly 1.5TB per month.

How about a slightly different tack. Download a new build if XX builds newer than the current installed one or YY days older. Keeping the install latest option to be run manually and setting the default XX to say 100 and YY to 1 week means that during times of high change you arent dishing out thousands of copies and during times of low change you still are getting one new a week.

Adding a 3rd option "install a community SVN stables" means we could force everyone up to update or downgrade in times of problems.

People could tweak their install preferences but setting the default to 1 a day will quickly require massive amounts of bandwidth.

As far as I know, when things are changed in SVN, the app has to be re-compiled. That is going to take time. It's not as simple as just swapping out a couple files. Sure there may be times when you actually could just swap out some files, but I am not going to spend my time trying to figure out when it is like that.