For example, this can be used to re-open a System Settings prefpane after an update has been installed. For plug-ins in Sparkle 2, set this to YES to re-launch the host targetted bundle instead of the application bundle. Set this to YES if you want to allow JavaScript in your release notes.ĭefault: NO. Optional alternative NSUserDefaults domain name if you don’t want to use the standard user defaults, for example when accessing preferences from an App Group suite.ĭefault: NO. “MyApp 3 4.0 is now available” vs “MyApp 4.0 is now available”. For example, if your bundle name already has a version number appended to it, setting this may help smooth out certain messages, e.g. Optional alternative bundle display name. This setting is available in Sparkle 2.5 and later. By default, Sparkle only allows clicks to links that have a safe known URL scheme (like https). Set this to NO to hide release notes display from the update alert.Īn array of custom URL schemes allowed to be clicked from Sparkle’s release notes view. Note this setting controls the default and users have the option to change this behavior.ĭefault: YES. In all versions of Sparkle, if the application hasn’t quit for 1 week the user will be presented with installing the downloaded update (unless the updater delegate overrides this). In Sparkle 2, updates will be downloaded but not installed automatically if authorization is required. In Sparkle 1, updates won’t be opted into this if users need to provide authorization. If set to YES, Sparkle will attempt to download and install new updates silently in the background. Enables automatic download and installation of updates by default. Set this to YES to always allow automatic updates even if automatic checking of updates is disabled.ĭefault: NO. Set this to NO to disallow automatic updates and require manual installation every time. Note: this has a minimum bound of 1 hour in order to keep you from accidentally overloading your servers.īy default, Sparkle automatically presents your users with the option to allow to automatically download and install any available updates if automatic checking of updates is enabled. This property can later be overridden by setting automaticall圜hecksForUpdates like in response to user setting changes.ĭefault: NO. Setting this to NO disables automatic checking for updates by default, also without asking your users for permission. Setting this to YES enables automatic checking for updates (but not installation) by default, without asking your users for permission first. As of Sparkle 2.4 or later, the user will also have an option to opt into or out of automatic downloading of updates the default state is based on the SUAutomaticallyUpdate setting. If permission is granted, automatic checks for updates then becomes enabled. Use Sparkle’s generate_keys tool to get it.īy default when this is not set, automatic checking for updates is initially disabled but users will be prompted for permission for Sparkle to check for updates automatically on second launch. It’s recommended to always set it in ist, even if you change it later programmatically. Here are the main routes by which you can bend Sparkle’s behavior to your will: ist Settings Key
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |