markcarver/Sparkle — comment on commit 3f1d59343168237e760951cb6026b26b8a6f9b34
File:  line 0
By markcarver:

A lot of this is for background updating (with automatic download and install).

Because the `finish_installation` is, now, not only responsible for restarting the application but also installing it... it has broke some of the delegate method selector names (and functionality):

`mayUpdateAndRestart` calls the delegate method `updaterShouldRelaunchApplication:`. If the delegate returns `NO` then `installWithToolAndRelaunch:` will abort the update.

This was an attempt to clarify the delegate methods for when they should really be called.

As far as `updaterShouldPromptInstall:` goes, I'll admit.. this is for somewhat a case support in where the application requires the run-loop (in this case the updater) to terminate the application based on the update finishing successfully or `update:didAbortWithError:`.

Rright now, with `SUAutomaticUpdateDriver`, Sparkle will wait for the 7 days before it will eventually show the alert dialog and prompt the user to install and restart. This delegate method allows the delegate to bypass this alert altogether and invoke `installWithToolAndRelaunch:`

see the last commit of mstratman/cocoadialog#18 for actual usage