From: Michael Niedermayer <michaelni@gmx.at>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: suggestions for gitweb
Date: Mon, 14 May 2007 10:53:15 +0200 [thread overview]
Message-ID: <20070514085314.GY14859@MichaelsNB> (raw)
In-Reply-To: <20070514023609.GI18276@pasky.or.cz>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
Hi
On Mon, May 14, 2007 at 04:36:09AM +0200, Petr Baudis wrote:
> On Mon, May 14, 2007 at 04:00:02AM CEST, Michael Niedermayer wrote:
> > i agree with you that she will click on 'history' and figure out what it is
> > but if she wants to see the contents of one of the files then i think
> > she will be confused and not know where to click,
>
> I think she will just click on the filename - straightforward enough...?
yes and no :)
i see 2 possible problems with this
first if she starts from the summary page (which is from where she would
start from if she clicked on 'ffmpeg') then she would see the recent
history but no directory/file names, she would have to click on 'tree'
here
the second possible problem i see is that while directory names are
displayed in iceweasel in underlined blue like links, filenames are
not, so she might not realize that she can click on them
another thing i just realized is that the blob/tree links on the tree
page seems redundant as the directory/file names already link to these
pages, iam just mentioning that as some people in this thread seemed to
like minimizing the number of links and the length of varous displayed
items
also file size and last modified dates would be interresting on the tree
page
viewvc displays on its equivalent page, time since last change
svn revission of the last change, the author/commiter of the last change
and the corresponding abbreviated log entry
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-14 8:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 20:55 suggestions for gitweb Michael Niedermayer
2007-05-12 22:39 ` Junio C Hamano
2007-05-12 23:15 ` Aaron Gray
2007-05-13 0:41 ` Jakub Narebski
2007-05-13 0:54 ` Junio C Hamano
2007-05-13 11:50 ` Jakub Narebski
2007-05-13 16:52 ` Lars Hjemli
2007-05-14 7:31 ` Suggestions for cgit (was: Re: suggestions for gitweb) Jakub Narebski
2007-05-14 8:50 ` Lars Hjemli
2007-05-15 12:57 ` Lars Hjemli
2007-05-13 0:01 ` suggestions for gitweb Michael Niedermayer
2007-05-13 11:18 ` Jakub Narebski
2007-05-14 0:28 ` Junio C Hamano
2007-05-14 1:08 ` Petr Baudis
2007-05-14 2:00 ` Michael Niedermayer
2007-05-14 2:36 ` Petr Baudis
2007-05-14 8:53 ` Michael Niedermayer [this message]
2007-05-14 9:58 ` Petr Baudis
2007-05-14 16:49 ` Jakub Narebski
2007-05-14 17:37 ` Michael Niedermayer
2007-05-15 15:46 ` Jan Hudec
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=20070514085314.GY14859@MichaelsNB \
--to=michaelni@gmx.at \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).