From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Cuirass enhancements
Date: Mon, 24 Jun 2019 00:08:23 +0200 [thread overview]
Message-ID: <20190624000823.1734d359@alma-ubu> (raw)
In-Reply-To: <87muidmk2p.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Wed, 19 Jun 2019 21:49:50 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
> > On Tue, 18 Jun 2019 19:50:25 +0200
> > Björn Höfling <bjoern.hoefling@bjoernhoefling.de> wrote:
> >
> >> * I would like to know that I'm on page k/n.
> >
> > That web interface is a frontend to a dynamically changing database
> > (and a quickly changing database at that).
> >
> > What would "page" even mean there?
>
> Since real constant pages are impossible (or can only be approximated)
> I’d like to know just how far to the beginning or end I am.
>
> It doesn’t need to be a number. If it was just a line at the bottom
> with a marker near the beginning, the middle, or the end, and
> adjusting its position as I go to the next or previous page I’d
> already be happy.
You are right Danny, I haven't considered the fact that content changes
(at least for the not yet finished evaluations). I like Ricardo's idea:
I don't care about being exaclty on page 23/204. I just want some
notion of where I am: At the beginning, the end, or roughly somewhere
in between.
Still I like the greyed-out buttons to know that I'm really at the
beginning/end, and that the buttons are consistent.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-06-23 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 17:50 Cuirass enhancements Björn Höfling
2019-06-18 20:52 ` Ricardo Wurmus
2019-06-18 22:19 ` Ricardo Wurmus
2019-06-19 7:49 ` Ricardo Wurmus
2019-06-19 8:23 ` Ricardo Wurmus
2019-06-19 10:16 ` Björn Höfling
2019-06-19 13:45 ` Ricardo Wurmus
2019-06-19 13:55 ` Ricardo Wurmus
2019-06-19 16:07 ` Danny Milosavljevic
2019-06-19 19:49 ` Ricardo Wurmus
2019-06-23 22:08 ` Björn Höfling [this message]
2019-06-21 15:18 ` Ludovic Courtès
2019-06-23 22:02 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190624000823.1734d359@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).