Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One-click automatic updates / "update on next launch" #22774

Open
cbjeukendrup opened this issue May 11, 2024 · 1 comment
Open

One-click automatic updates / "update on next launch" #22774

cbjeukendrup opened this issue May 11, 2024 · 1 comment
Assignees
Labels
feature request Used to suggest improvements or new capabilities updates

Comments

@cbjeukendrup
Copy link
Contributor

Some apps, most notably ones using the Electron framework, provide very convenient ways of automatically installing updates. For example,

  • VSCode, GitHub Desktop and Discord download updates in the background, and then display a button that lets you install the update and relaunch the app, all with just one click.
  • Figma displays a popup message when there is an update, with the options to install it right now or the next time that you launch the app.

All of these apps make use of the Squirrel framework, which is built into Electron.

In MuseScore 3, the situation was similar to that: it made use of the Sparkle framework on macOS, and the WinSparkle port of that on Windows.

In MuseScore 4, we use our own solution, but unfortunately this doesn't go further than just downloading the update "in the foreground" and then letting the user install it manually. This has some disadvantages:

  • it takes time and is not very convenient, possibly resulting in users endlessly deferring the update
  • it's limiting us: for example, we didn't change the filename of the macOS app from "MuseScore 4" to "MuseScore Studio", because by keeping it unchanged, the OS will offer to overwrite the old version, and that is essential because many users won't be able to locate the old version themselves and delete it manually, so they would end up with two versions which would definitely cause confusion. An automatic update solution could take care of situations like that.
@cbjeukendrup cbjeukendrup added feature request Used to suggest improvements or new capabilities updates labels May 11, 2024
@shoogle
Copy link
Contributor

shoogle commented May 11, 2024

Maybe we could do most of the download and installation in the background, extracting all the files to a temporary folder, then when we prompt the user to relaunch MuseScore, all we need to do is rename the temporary folder to put everything in the final, proper location.

@bkunda bkunda self-assigned this May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities updates
Projects
None yet
Development

No branches or pull requests

3 participants