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

xqemu-manager should download xqemu for ease of use #17

Open
MayeulC opened this issue Jul 11, 2018 · 1 comment
Open

xqemu-manager should download xqemu for ease of use #17

MayeulC opened this issue Jul 11, 2018 · 1 comment

Comments

@MayeulC
Copy link

MayeulC commented Jul 11, 2018

As discussed on IM, this would greatly improve usability for first-time users, especially windows users, that are used to easy first-time setups.

That's why I would like to make it a wizard for the first xqemu run:

  1. Warn the user that their MCPX and Kernel are needed for now, with two browsing fields just under it
  2. Offer to download the HDD image (a browse button, with a download button next to it)
  3. Offer to download xqemu. I can see a dropdown with the 10 latest artifacts or so, and a download button next to it, plus a browse button.

The wizard could accommodate other settings in the future, such as input, and console configuration (region, etc). But those three steps are the most important for first time users. Of course, the wizard would be cancellable, launchable again, pages could be skipped, and the downloaders could be called again directly from the settings.

An update check could also be performed on launch, and offer the user to upgrade if a new one is available.


As a reference, these were my alternative proposals to make the setup easier:

  • creating a repo with xqemu-manager and xqemu as submodules, that would compile both
  • changing the xqemu appveyor script to include xqemu-manager
  • xqemu manager could be a frontend that lists and downloads (or compiles!) specific revisions. That might be a better solution for the user.
@GXTX
Copy link
Contributor

GXTX commented Nov 6, 2018

There was some talk in xqemu/xqemu#18 about including xqemu-manager with the AppVeyor artifacts. One of the ideas brought up was auto-updating (of xqemu-manager and/or xqemu). I don't believe auto-update should be included, or at the very least not defaulted on.

I've been personally burned by programs having auto-update enabled and having update servers get hacked (most notably puush). I understand the data would be coming from the official AppVeyor account for the XQEMU project but things can still happen that are undesirable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants