Re: suggestions for gitweb
- From
- Jan Hudec <bulb@ucw.cz>
- Date
- May 15, 2007, 15:46 UTC
- Message-ID
- <20070515154613.GB3653@efreet.light.src>
- In-Reply-To
- <20070514020001.GX14859@MichaelsNB>
Hello,
On Mon, May 14, 2007 at 04:00:02 +0200, Michael Niedermayer wrote:
Show 9 quoted lines
> 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>