From: Jan Hudec <bulb@ucw.cz>
To: Michael Niedermayer <michaelni@gmx.at>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: suggestions for gitweb
Date: Tue, 15 May 2007 17:46:13 +0200 [thread overview]
Message-ID: <20070515154613.GB3653@efreet.light.src> (raw)
In-Reply-To: <20070514020001.GX14859@MichaelsNB>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
Hello,
On Mon, May 14, 2007 at 04:00:02 +0200, Michael Niedermayer wrote:
> On Mon, May 14, 2007 at 03:08:31AM +0200, Petr Baudis wrote:
> > But, even if that's the case, when a new user meets gitweb and looks
> > at the 'history' link, what do you think she will do? Start hunting the
> > page for some link to a glossary? I yet have to see a user like that :-)
> > - I will bet that she just clicks at the link and figures out what it is
> > about based on what happenned.
>
> 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
Well, before clicking it, she will move the mouse pointer over it. And either
look for tooltip -- which sadly won't come up -- or read the url -- with
sadly isn't much help.
> she will be confused and not know where to click, and a 'help' link which
> would lead to a page which explains what 'blob' is at the top of the page
> would solve that with less frustration than random clicking around
IMHO providing tooltips would probably solve it with even less frustration.
If the user comes to the page, she will probably quickly notice, that the
links have tooltips. And than going over all the links with the pointer and
reading the tooltips is a lot easier and faster than switching to a help
page. Besides people don't want to admit, even to themselves, they don't
understand something to a point they should read the docs, so they won't read
it. But anybody will read the tooltips -- they don't look like docs.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-15 15:46 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
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 [this message]
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=20070515154613.GB3653@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=michaelni@gmx.at \
--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).