public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/2] Improve behavior after download error
Date: Tue, 07 Nov 2017 18:56:00 -0000	[thread overview]
Message-ID: <f391b1c9-93f8-5f3f-2cd4-bc0ca8bd8d11@dronecode.org.uk> (raw)
In-Reply-To: <d3b64e50-5c14-b72f-49da-4dfb54b4335f@SystematicSw.ab.ca>

On 07/11/2017 04:28, Brian Inglis wrote:
> On 2017-11-06 14:49, Ken Brown wrote:
>> This is a followup to
>> https://sourceware.org/ml/cygwin-apps/2017-11/msg00003.html.  The
>> focus of that thread was a crash that occurs on the topic/libsolv
>> branch.  Here I'm more interested in a UI issue.  Namely, I don't
>> think it's reasonable that setup goes back to the site page if the
>> user clicks Yes in response to "Download Incomplete. Try again?".
>> This is not what the message says will happen, and I'm not convinced
>> that it even works right if the user changes mirrors after being sent
>> to the site page.
> 
> Would it make more sense to drop to the package chooser page, after issuing the
> error message and advising the user to: select Back to go to the package chooser
> page, select Next to retry the downloads, or select Cancel to exit?

Do we actually report the package name for the failed download so that 
the user could make an informed change in the package chooser?

In any case, this is an incremental improvement, especially over the 
utterly mad thing we are currently doing in unattended mode.

  reply	other threads:[~2017-11-07 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 21:49 Ken Brown
2017-11-06 21:49 ` [PATCH setup 2/2] Whitespace fixes Ken Brown
2017-11-06 21:49 ` [PATCH setup 1/2] Improve behavior after download error Ken Brown
2017-11-07  4:28 ` [PATCH setup 0/2] " Brian Inglis
2017-11-07 18:56   ` Jon Turney [this message]
2017-11-08 14:35     ` Ken Brown
2017-11-08 18:52       ` Brian Inglis
2017-11-09 13:21         ` Jon Turney
2017-11-09 16:42           ` Ken Brown
2017-11-10 14:41             ` Ken Brown
2017-11-08 18:46     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f391b1c9-93f8-5f3f-2cd4-bc0ca8bd8d11@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).