git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: Show trailing slash when listing tree entry in tree listing
Date: Sat, 07 Oct 2006 23:27:08 +0200	[thread overview]
Message-ID: <eg961o$2v7$2@sea.gmane.org> (raw)
In-Reply-To: 20061007211531.GH20017@pasky.or.cz

Petr Baudis wrote:

> Dear diary, on Sat, Oct 07, 2006 at 10:38:51PM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
>> Petr Baudis wrote:
>> 
>> > So, I'd like to either have the view links or the filenames in classical
>> > link style so that it's apparent they are clickable; I didn't post a
>> > patch since I didn't have time/energy to fight for it yet. ;-)
>> 
>> There is a tradeout. Either have easily distinguishable directories and
>> files, by using both different color and decoration (underline), or we have
>> filename/directory name clearly marked as link. One or the other.
>> 
>> That is why I'd rather have this "redundant" blob/tree link (perhaps in
>> separate column).
> 
> As I suggested in another mail, perhaps the whole problem is wrong and
> you shouldn't have to dug for trees in a bunch of blobs in the first
> place - let's group all the trees at the top, as all the well-behaved
> directory listings do.

It is a good idea, although we would wither to have to read the directory
(tree) listing first into some array, then sort it directories first
(contrary to current output while reading, which reduces latency provided
that browser can properly display partial contents), or add some option
to git-ls-tree command to output tree entries (directories) first, instead
of sorting by filename.

>> But this is a matter of policy, unless we want to add theme support to
>> gitweb ;-))
> 
> We _do_ have that - you can supply your own gitweb.css. But the defaults
> should be sensible.

Theme support, as to be able to choose theme, like style selectable from
web browser, and for example choosing if the tree/blob links are present
or not. Some of which might be done via CSS (display:none).
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2006-10-07 21:27 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 19:22 [PATCH] gitweb: Do not print "log" and "shortlog" redundantly in commit view Luben Tuikov
2006-10-06  7:44 ` Jakub Narebski
2006-10-06 16:35   ` Petr Baudis
2006-10-06 22:16   ` Luben Tuikov
2006-10-07 13:24     ` Petr Baudis
2006-10-07 14:05       ` Jakub Narebski
2006-10-07 14:17         ` Petr Baudis
2006-10-07 14:10       ` [PATCH 1/2] gitweb: Show snapshot links for tree entries in tree listing Petr Baudis
2006-10-07 18:37         ` Luben Tuikov
2006-10-07 18:41           ` Petr Baudis
2006-10-07 18:52             ` Luben Tuikov
2006-10-07 19:15               ` Petr Baudis
2006-10-07 22:31                 ` Junio C Hamano
2006-10-08  1:04                 ` Luben Tuikov
2006-10-07 14:10       ` [PATCH 2/2] gitweb: Show trailing slash when listing tree entry " Petr Baudis
2006-10-07 18:44         ` Luben Tuikov
2006-10-07 19:06           ` Jakub Narebski
2006-10-07 19:12             ` Petr Baudis
2006-10-07 20:38               ` Jakub Narebski
2006-10-07 21:15                 ` Petr Baudis
2006-10-07 21:27                   ` Jakub Narebski [this message]
2006-10-09 20:55               ` Petr Baudis
2006-10-09 22:52                 ` Junio C Hamano
2006-10-10  5:10                   ` Junio C Hamano
2006-10-10  5:38                     ` Luben Tuikov
2006-10-10  5:46                       ` Junio C Hamano
2006-10-10  6:34                         ` Luben Tuikov
2006-10-10  5:46                       ` Jeff King
2006-10-10  6:41                         ` Luben Tuikov
2006-10-10  6:58                           ` Jeff King
2006-10-10  9:15                       ` Jakub Narebski
2006-10-10 19:19                         ` Luben Tuikov
2006-10-10 19:57                           ` Junio C Hamano
2006-10-10 20:31                             ` Jakub Narebski
2006-10-10 21:02                               ` Luben Tuikov
2006-10-10 21:13                                 ` Jakub Narebski
2006-10-10 22:18                                   ` Luben Tuikov
2006-10-10 20:52                             ` Luben Tuikov
2006-10-10 21:00                               ` Jakub Narebski
2006-10-10 22:14                                 ` Luben Tuikov
2006-10-10 22:40                                   ` Jakub Narebski
2006-10-10 20:29                           ` Jakub Narebski
2006-10-11 15:35                           ` Andreas Ericsson
2006-10-10  6:21                 ` Luben Tuikov
2006-10-10  7:05                   ` Jeff King
2006-10-10  8:07                     ` Andreas Ericsson
2006-10-10 13:14                       ` Josef Weidendorfer
2006-10-10 18:23                         ` Luben Tuikov
2006-10-10 18:52                           ` Josef Weidendorfer
2006-10-10 18:50                         ` Luben Tuikov
2006-10-10  8:28                     ` Junio C Hamano
2006-10-07 21:31           ` A Large Angry SCM
2006-10-07 22:34           ` Junio C Hamano
2006-10-08  1:16             ` Luben Tuikov

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='eg961o$2v7$2@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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).