all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Cuirass enhancements
Date: Wed, 19 Jun 2019 18:07:31 +0200	[thread overview]
Message-ID: <20190619180731.1eaf1ed6@scratchpost.org> (raw)
In-Reply-To: <20190618195025.62b32955@alma-ubu>

[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]

Hi Björn,

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?

And the "/n" part is impossible to keep constant because the database changes
and so does n.
So the "/n" part on the display would keep changing--and it would be correct
in doing so.  Furthermore, the page number you are *on* would also keep
changing.

Even if there were fixed-layout "page"s, the way the database is
structured means that having pagination show a fixed number of items
per page at all is difficult to do (cuirass tries to do it).

Alternatively, the server could keep a serializable transaction
open per client session.
Then you just wouldn't see new builds until you somehow restarted your
client session (HTTP is stateless--so more fakery necessary there).
Then you can have page numbers :)

> I'm at the first tab. "Previous" is greyed out.

I don't like this graying out business.  It's perfectly possible that a new
entry appeared in the database that is now (because of the sorting) before what
you thought was the first page (because back then when you queried the page it
*was* the first page--emphasis on "was")--and now you can't get to it.

> Then I would expect
> "First" also to be greyed out: If I cannot go any further back, I am on
> the "First" tab (linear, consecutive order of tabs assumed :-))

I've made "First" and "Last" behave the way you expect in cuirass commit
d5b827097b456100039370003899ec7ad04ac934.  However, that is not
an endorsement of graying out.  I just like consistency.
 
> Even worse at the end: I can click four times on "Next", and then be at
> a page that shows only three jobs (the total number of jobs is not
> always dividable by the number of jobs per page, so the last page
> usually has a smaller remainder to show):
> https://ci.guix.gnu.org/eval/5862?border-high-time=1560816540&border-high-id=1398862
> So, I cannot go any NEXTer, that button is greyed out. As with the
> beginning, I'm expecting to be already on the LAST page. But the button
> is clickable. And when I click it, I will receive a FULL PAGE! 

Yeah, well, pages don't exist and cuirass in imperfectly faking them.

I'd go back to first principles and ask what problem the paging is supposed to
solve, then solve it in a different way.  It's already very different to what
book pages would be.

Suggestions welcome.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-06-19 16:07 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 [this message]
2019-06-19 19:49   ` Ricardo Wurmus
2019-06-23 22:08     ` Björn Höfling
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

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

  git send-email \
    --in-reply-to=20190619180731.1eaf1ed6@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.