List for cgit developers and users
 help / color / mirror / Atom feed
From: jamie.couture at gmail.com (Jamie Couture)
Subject: [PATCH] repolist pagination changes
Date: Mon,  8 Oct 2012 12:49:34 -0400	[thread overview]
Message-ID: <1349714974-10512-1-git-send-email-jamie.couture@gmail.com> (raw)
In-Reply-To: <CAHmME9qQv5QDk=48kdV0sYxS5nuv7KVm_anGOZ1Q4Vff-1q7=Q@mail.gmail.com>

bold the current page we're viewing

Signed-off-by: Jamie Couture <jamie.couture at gmail.com>
---
 cgit.css      |  4 ++++
 ui-repolist.c | 11 +++++++----
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/cgit.css b/cgit.css
index 651a320..54da076 100644
--- a/cgit.css
+++ b/cgit.css
@@ -548,6 +548,10 @@ div#cgit div.pager a {
 	margin: 0em 0.5em;
 }
 
+div#cgit div.pager .current {
+	font-weight: bold;
+}
+
 div#cgit span.age-mins {
 	font-weight: bold;
 	color: #080;
diff --git a/ui-repolist.c b/ui-repolist.c
index 943eaab..46cbacf 100644
--- a/ui-repolist.c
+++ b/ui-repolist.c
@@ -123,11 +123,14 @@ void print_header(int columns)
 
 void print_pager(int items, int pagelen, char *search, char *sort)
 {
-	int i;
+	int i, ofs;
+	char *class = NULL;
 	html("<div class='pager'>");
-	for(i = 0; i * pagelen < items; i++)
-		cgit_index_link(fmt("[%d]", i+1), fmt("Page %d", i+1), NULL,
-				search, sort, i * pagelen);
+	for(i = 0, ofs = 0; ofs < items; i++, ofs = i * pagelen) {
+		class = (ctx.qry.ofs == ofs) ? "current" : NULL;
+		cgit_index_link(fmt("[%d]", i+1), fmt("Page %d", i+1), class,
+				search, sort, ofs);
+	}
 	html("</div>");
 }
 
-- 
1.7.11.4





  parent reply	other threads:[~2012-10-08 16:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  1:39 Maintaining My Own Cgit Tree Jason
2012-09-27  4:22 ` william.bell
2012-09-27  9:00   ` Tobias.Bieniek
2012-09-27 15:53   ` webmaster
2012-09-29  0:30 ` [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
2012-09-29  5:20   ` Jason
2012-09-29 18:43     ` lsworkemail112
2012-09-29 18:51       ` Jason
2012-09-29 19:14         ` lsworkemail112
2012-09-29 19:15           ` Jason
2012-09-29 19:17             ` lsworkemail112
2012-09-29 19:16           ` lsworkemail112
2012-09-30  5:51       ` mailings
2012-09-30 17:28         ` lsworkemail112
2012-09-30 17:29         ` Jason
2012-09-30 17:40           ` mailings
2012-09-30 21:06           ` lsworkemail112
2012-09-30 21:33             ` Jason
2012-10-01  6:12               ` mailings
2012-10-02  1:46                 ` lsworkemail112
2012-10-02  2:04                   ` Jason
2012-10-02  2:08                     ` lsworkemail112
2012-10-01 13:56       ` webmaster
2012-10-08 16:48 ` [PATCH 1/2] add git config parsing during scan-path jamie.couture
2012-10-08 16:48   ` [PATCH 2/2] update documentation jamie.couture
2012-10-08 21:05     ` 
2012-10-08 21:18     ` 
2012-10-08 16:49 ` jamie.couture [this message]
2012-10-08 21:39   ` [PATCH] repolist pagination changes Jason
2012-10-08 17:12 ` [PATCH] add tag target to generate ctags jamie.couture
2012-10-08 21:41   ` Jason
2012-10-09 10:56 ` [PATCH] add git config parsing during scan-path jamie.couture
2012-10-09 11:33   ` Jason
2012-10-09 11:15 ` Maintaining My Own Cgit Tree mailings
2012-10-09 11:18   ` Jason
  -- strict thread matches above, loose matches on Subject: below --
2011-11-13 22:08 [PATCH] repolist pagination changes jamie.couture

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=1349714974-10512-1-git-send-email-jamie.couture@gmail.com \
    --to=cgit@lists.zx2c4.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 NNTP newsgroup(s).