From: andy.doan at linaro.org (Andy Doan)
Subject: [PATCHv2 0/2] Collapsible Section Support
Date: Mon, 3 Oct 2016 10:44:18 -0500 [thread overview]
Message-ID: <b8dfdcde-8ca4-4972-3284-06169d84567b@linaro.org> (raw)
In-Reply-To: <CAHmME9oNe7pSPuiDDFdST1bagyGTDzNaV8AQ1TyxVqbui7WRYw@mail.gmail.com>
On 10/01/2016 03:50 PM, Jason A. Donenfeld wrote:
> Hey Andy,
>
> One issue with this is -- isn't this the sort of thing that would be
> better taken care of with css3 or css+javascript? That is to say you
> list the children of some elements as being display:none until they're
> clicked, and then upon click you make it visible? This seems like it'd
> be a bit slicker of an interface too. Would this be an acceptable
> interface?
That's okay with me and I'll work up a patch to demonstrate it. For a
company with many repos like Linaro, not displaying them does make the
front page load faster, but I've already sensed momentary confusion when
people try out our UI:
https://git-ap.linaro.org/cgit/
I'll work up a dynamic version this today and throw it on another Linaro
mirror so you can compare the differences.
next prev parent reply other threads:[~2016-10-03 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:01 andy.doan
2016-09-12 22:01 ` [PATCH 1/2] ui-repolist: provide hyperlinks on section names andy.doan
2016-09-12 23:08 ` john
2016-09-12 22:01 ` [PATCH 2/2] ui-repolist: Allow sections to be collapsible andy.doan
2016-09-13 3:54 ` [PATCHv3 0/2] Collapsible Section Support andy.doan
2016-09-13 3:54 ` [PATCHv3 1/2] ui-repolist: provide hyperlinks on section names andy.doan
2016-09-13 3:54 ` [PATCHv3 2/2] ui-repolist: Allow sections to be collapsible andy.doan
2016-10-01 20:50 ` [PATCHv2 0/2] Collapsible Section Support Jason
2016-10-03 15:44 ` andy.doan [this message]
2016-10-03 15:54 ` Jason
2016-10-03 15:56 ` Jason
2016-10-03 18:04 ` andy.doan
2016-10-03 20:52 ` andy.doan
2016-10-11 16:15 ` andy.doan
2016-10-03 18:10 ` tim
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=b8dfdcde-8ca4-4972-3284-06169d84567b@linaro.org \
--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).