public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wayne Davison <wayne@opencoder.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: setup 2.895 release candidate - please test
Date: Sun, 16 Dec 2018 20:44:00 -0000	[thread overview]
Message-ID: <CAHSx_Sv=W3058Hdf0Kq4HRso21kCSZ1y0xv2MbSKWOiMAqp5ig@mail.gmail.com> (raw)
In-Reply-To: <7918cc00-17e9-45dc-0b32-085a9d49b099@dronecode.org.uk>

On Sun, Dec 16, 2018 at 6:52 AM Jon Turney wrote:
> I was hoping to look at improving the 'skip' -> 'install current
> version' flow (which used to be a single click, but now requires you to
> pick the latest non-test version)

That's a nice idea for a future change. I'd suggest making it where
you can click on the "bin?" checkbox and have it switch from "Skip" to
the latest version. It already cycles between a few values (such as
Uninstall and Reinstall, depending on the state of the package) but it
will not return the drop-down back to "Skip" for an installed package,
nor will it return back to the new version number on a pending update
(when pressing the checkbox multiple times).

One other suggestion I'd love to see would be to group the uninstall &
install lines in the list of upcoming actions into a single line, so
that instead of the user thinking that a package is going away (e.g.
in a really long list of uninstall lines) it says something like
"Updating FOO from VER1 to VER2".  As an alternative, if the uninstall
line said "(for an update)" instead of "(automatically added)" that
would have less potential for confusion.


..wayne..

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2018-12-16 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 16:12 Jon Turney
2018-11-06 10:29 ` Marco Atzeri
2018-11-06 17:16   ` Marco Atzeri
2018-12-06  9:12 ` Marco Atzeri
2018-12-16 14:52   ` Jon Turney
2018-12-16 20:44     ` Wayne Davison [this message]

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='CAHSx_Sv=W3058Hdf0Kq4HRso21kCSZ1y0xv2MbSKWOiMAqp5ig@mail.gmail.com' \
    --to=wayne@opencoder.net \
    --cc=cygwin@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).