You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want CodeEdit to be evergreen, meaning it automatically downloads updates in the background. When the user closes or restarts, CodeEdit installs the downloaded update in the background. When an update is downloaded, the user gets a notification via notification center which allows them to install and restart then. If dismissed it will install on application close. There will be a "Automatically keep CodeEdit up to date" checkbox (enabled by default) that controls this behavior.
Can the Sparkle Framework do this? Looking at the docs, I see the SUAutomaticallyUpdate property, which says
Default: NO. Enables automatic download and installation of updates. If set to YES, Sparkle will attempt to download and install new updates silently in the background. In Sparkle 1, updates won’t be opted into this if users need to provide authorization. In Sparkle 2, updates will be downloaded but not installed automatically if authorization is required. 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).
If we prompt the user for authentication the first time but then auto-update, wouldn't this fulfill the evergreen goal after the first launch and authentication prompt?
Activity
[-]Non-interruptive Background Updates[/-][+]✨ Non-interruptive Background Updates[/+]tommyming commentedon Oct 17, 2022
@austincondiff Hello, I would like to work on this issue, may I have more information about this? Thanks.
austincondiff commentedon Oct 17, 2022
@tommyming Added details above. Let me know if you have any additional questions.
MrDevel0per commentedon Jan 14, 2023
Can the Sparkle Framework do this? Looking at the docs, I see the
SUAutomaticallyUpdateproperty, which saysIf we prompt the user for authentication the first time but then auto-update, wouldn't this fulfill the evergreen goal after the first launch and authentication prompt?
austincondiff commentedon Jan 14, 2023
Yes. I believe so. Is this something you’d be willing to take on?
MrDevel0per commentedon Jan 14, 2023
@austincondiff I will try to take this on to the best of my ability.