Thoughts on update

[arpit]

So the one feature I really want to put in to the LogBook (and other
air projects going forward) is an autoupdate feature. AIR handles the
actual application updates pretty nicely, but I just want to implement
a good workflow for end users.

Kevin did some work on an update manager based on the
airremoteupdater project (http://codeazur.com.br/lab/
airremoteupdater/) that we should now roll into the project.
The code right checks if an update is needed and can prompt the user
for an update required message. It does so by loading the latest air
app from the remote directory (so we have to make sure the latest app
can always be referenced from a consistant url), unzipping the
application's app descriptor and checking the latest version with the
version installed.

However I dont really want the updater to check everytime LogBook is
launched, so I want to wrap that a little more in an utility class
with an updatePolicy parameter. The policy can be something like
EVERY_LAUNCH, ONCE_A_WEEK, ONCE_A_MONTH etc.

Is that overkill ? Thoughts ?

[Kevin Fitzpatrick]

That was right along the same lines as I was thinking.

We would have to have a latest-release .AIR file sitting around
publicly on the google code site somewhere.

- Kevin