Implement a /quiet installation to complement the new auto-updater

[aleab]

When a new update has been downloaded and is ready to be installed, if the user chooses to install it straight away, the installation should be as seamless as possible:

1. The user clicks "Install" in the message box.
2. The installer is launched with the /quiet parameter and proceeds without user input.
3. Toastify is terminated.
4. Toastify is restarted automatically after the update.

[Vankog]

some auto-updater thoughts from user's perspective for discussion:

• As an informed/interested user, I'd like to see the changelog before I decide to hit "Update".
• As a user in general, why should I open the folder of the downloaded setup? (auto download enabled)
• As a user who:
  • does not care about updates ("Bah, I don't care! Never touch a running system!")
  • or is annoyed by update processes ("Aw, come on! Always these stupid updates when I just want to use this program! .... CANCEL!")
  • or is a typical parent/grandparent with not enough knowledge ("Son? Yes? Hello, I'm just calling, because the PC seems broken. It always tells me to update or go to a Gif-Up or something. What should I click?"): -> I'd like to have updates handled seamlessly, without any user interaction at all.

(the scenarios in the third entry are all taken from my personal experience with friends and family members...)

[aleab]

1. That's why there's the "Go to GitHub" button. I'll probably change it to "Show changelog" instead, but that will only show the changelog of the latest version; I still have to work on a full changelog viewer.
2. You may not want to install the update immediately, but at the same time you want to know where the installer has been downloaded, so that you don't have to download it a second time.
3. No user interaction at all is not really possible. Or rather, does not provide a great experience for the user. Imagine:
   • Best case scenario – you are listening to some music and using the hotkeys; the update starts in the background, Toastify has to be terminated and your hotkeys don't work anymore; you are like "WTF is happening?! I've been hacked!"
   • Worst case scenario – you are using the "Close Spotify when Toastify terminates" setting; your Spotify closes when the update starts in the background.

[Vankog]

1. I see. Well, I was just referring to some update dialogs I came across in the past. Like TortoiseSVN / TortoiseGit or Evernote or VLC (I think). They show the user an update dialog that directly embeds the changelog right away. I kind of like this approach. But nothing to really worry about. Showing the changelog afterwards is totally fine as well.
2. Good point. But shouldn't Toastify just handle this? Like with a "remind me later" option maybe?
3. Oh, I do not intent to have updates seamlessly while running. That'll be weird, I agree. I was rather thinking of a seamless update during Toastify startup. Like Spotify does it. It downloads the setup in the background and on the next startup (or upon hitting the restart notification) it just installs auto-magically.

[aleab]

2. I think that makes sense. That's doable.
3. This is doable as well! We could add a notification in the Settings window and/or display a flash toast (a couple of seconds) that if clicked starts the installation, and also have Toastify auto-update itselft upon restart. A flash toast is already used for the "Notify only" update mode, so that's ready to use.