public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup libsolv, v2] Let the user review added dependencies
Date: Tue, 23 Jan 2018 01:07:00 -0000	[thread overview]
Message-ID: <067a5ecd-0668-7252-4c4e-7363c4d52fae@SystematicSw.ab.ca> (raw)
In-Reply-To: <6ca910ae-c6ee-d6f5-94cf-7d0075977fe9@cornell.edu>

On 2018-01-22 15:40, Ken Brown wrote:
> On 1/22/2018 4:51 PM, Brian Inglis wrote:
>> On 2018-01-22 10:37, Ken Brown wrote:
>>> If the solver found no problems but added packages to resolve
>>> dependencies, ask the user whether they want to review the added
>>> packages before proceeding.
>>>
>>> If they answer Yes, go back to the chooser with the 'Pending' view
>>> selected.  The implementation adds several new members to the
>>> PrereqChecker class so that the latter can communicate with the
>>> chooser page.
>>
>> Would it not be better, quicker, and easier, and to just show the updated
>> Pending view directly and unconditionally, without another popup dialogue box?
>> I think that's what most of us would expect from a UI display: just update the
>> displayed packages, if not being asked for confirmation that we really want to
>> do something possibly detrimental.
> 
> Yes, I think you're right, in principle.  But I'm not sure exactly what the UI
> should do.  If we simply update the displayed packages when the user selects
> 'Next', won't the user wonder what's going on?  Can you suggest a way to make it
> clear that we've updated the display to reflect added dependencies and that
> we're waiting for final confirmation?

I see what you mean: we don't have a status line or any way to highlight added
dependencies which we could use to convey that, so unless the addition of
dependencies to the Pending view is visually very obvious, we need to use a
dialogue box to pass on the message, before proceeding from the Pending view.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

  reply	other threads:[~2018-01-23  1:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 17:37 Ken Brown
2018-01-22 21:51 ` Brian Inglis
2018-01-22 22:40   ` Ken Brown
2018-01-23  1:07     ` Brian Inglis [this message]
2018-01-23 15:05       ` cyg Simple
2018-01-24 20:30 ` Jon Turney
2018-01-25  3:25   ` Ken Brown
2018-01-25  3:57     ` Ken Brown
2018-01-28 18:11       ` Jon Turney

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=067a5ecd-0668-7252-4c4e-7363c4d52fae@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).