…Thanks to Christiaan Hofman for the patch.
Fixes from Matt Stevens: "For background applications (menu bar, completely UI-less, etc) there are a couple of issues with Sparkle notifications: - When prompts such as the initial prompt to enable update checking are displayed they can be hidden behind other windows since the background app is not in focus. This can cause problems, as these prompts run modally and can stop the application from functioning without the user knowing why. - If the update notification window is displayed and the user clicks away to another application, the window disappears and there is no way to get it back since there is no other UI to cause the app to activate. In this case the update should probably operate as a standard window since it is effectively operating as the application's UI."
…Sparkle. More super-unstable refactorings to come...
…ing the value to be set in the case that [foo setValue:a] is called when [foo value] == a.
Sparkle now gies visual indication that it's checking for updates when hte update's user initiated. ie: it pops up a status controller saying "checking for updates..." What was SUUserInitiatedUpdateDriver is now SUUIBasedUpdateDriver; SUUserInitiatedUpdateDriver now is a subclass of that, along with SUScheduledUpdateDriver. This is a happy little refactoring that let me remove some redundant code.
…tiaan Hofman, for pointing out that I am dumb.
…t methods, and made some types more specific; patch courtesy Sean McBride.
…in situ -- thanks for the help, Charles D. H. Williams.
…ttle method - ie, no more internetenable. Thanks to Steve Gehrman from CocoaTech. Also fixed a bug with the host app extension method, the recursive find-the-app-in-the-archive method, and made the extension comparison case insensitive for extraction purposes.