public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup libsolv, v2] Let the user review added dependencies
Date: Thu, 25 Jan 2018 03:25:00 -0000	[thread overview]
Message-ID: <62f01ff4-e3c8-58f0-531d-7f04e8199801@cornell.edu> (raw)
In-Reply-To: <038ab66c-2fa7-2aa2-a8f1-45cadfc2b127@dronecode.org.uk>

On 1/24/2018 3:30 PM, Jon Turney wrote:
> On 22/01/2018 17: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.
> 
> As discussed, this approach could be confusing.
> 
> Attached is a slightly different approach, which adds a new page to 
> review and confirm what actions we're going to take.
> 
> For the moment, this just contains a simple text report, but I guess 
> this could be extended e.g. to use a grid control, or give reasons for 
> why packages are being installed.

I like this a lot.  It's *much* better than my approach.

My only suggestion is that you rethink what the confirm page should do 
in "download only" mode.  Maybe that page could even be skipped.  But if 
you think the user should confirm the download, there's no need to 
mention "uninstall" actions, and "install" actions should be reported as 
"download".

Ken

  reply	other threads:[~2018-01-25  3:25 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
2018-01-23 15:05       ` cyg Simple
2018-01-24 20:30 ` Jon Turney
2018-01-25  3:25   ` Ken Brown [this message]
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=62f01ff4-e3c8-58f0-531d-7f04e8199801@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).