From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: tree view: eliminate redundant "blob"
Date: Tue, 26 Sep 2006 22:31:58 +0200 [thread overview]
Message-ID: <efc2no$eti$2@sea.gmane.org> (raw)
In-Reply-To: 20060926201433.46979.qmail@web31810.mail.mud.yahoo.com
Luben Tuikov wrote:
> Jakub,
>
> I understand your argument completely. Underlining/coloring/etc
> entities which are "links" themselves was very cool circa 1993 when
> I took an HTML course (NSA Mosaic or rather...), transitioning from
> "gopher" to the WWW.
>
> Over the years I've seen a transition where web content is more and
> more context sensitive, i.e. everything you can see is in some way
> "clickable". Be it letters, words, sentences, graphical objects of
> some sort, etc. If you could imagine: any web content being a "wiki
> on steroids".
>
> Generally, this WEB Development argument goes as follows:
> "There is no reason for anything to not be clickable."
>
> Thus, I like the fact that gitweb is on the forefront of WEB development.
> We should keep it like that.
This is example of where forefront has it wrong. I'm all for "list" entry
to be link to default view, but I'm all against removing clearly marked
link to "plain"/"tree" view.
And "invisible links" _especially_ if the link is not convenience only
(i.e. it is not provided clearly as link somewhere else) is so called
"mystery meat navigation" and is one of the most common mistakes in
web development.
And is not as if "plain |" takes much space...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-26 20:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 5:38 [PATCH] gitweb: tree view: eliminate redundant "blob" Luben Tuikov
2006-09-26 6:34 ` Junio C Hamano
2006-09-26 17:04 ` Luben Tuikov
2006-09-26 8:54 ` Jakub Narebski
2006-09-26 9:22 ` Jakub Narebski
2006-09-26 16:07 ` Petr Baudis
2006-09-26 16:24 ` Jakub Narebski
2006-09-26 20:33 ` Luben Tuikov
2006-09-27 2:40 ` Junio C Hamano
2006-10-01 18:49 ` Jakub Narebski
2006-09-26 20:14 ` Luben Tuikov
2006-09-26 20:31 ` Jakub Narebski [this message]
2006-09-26 21:32 ` Luben Tuikov
2006-09-26 22:24 ` Jakub Narebski
2006-09-26 22:30 ` Jakub Narebski
2006-09-27 6:42 ` Junio C Hamano
2006-10-01 18:41 ` Jakub Narebski
2006-10-01 18:56 ` Junio C Hamano
2006-10-01 19:27 ` Jakub Narebski
2006-10-02 7:15 ` Andreas Ericsson
2006-10-02 10:56 ` Jakub Narebski
2006-10-02 7:34 ` Junio C Hamano
2006-10-02 11:06 ` Jakub Narebski
2006-10-02 19:46 ` Luben Tuikov
2006-10-02 19:11 ` Luben Tuikov
2006-10-02 20:03 ` Jakub Narebski
2006-10-03 4:14 ` Junio C Hamano
2006-10-03 8:18 ` Jakub Narebski
2006-10-03 9:34 ` Junio C Hamano
2006-10-03 10:15 ` Jakub Narebski
2006-10-05 0:15 ` Luben Tuikov
2006-10-03 20:20 ` Luben Tuikov
2006-10-03 16:31 ` Linus Torvalds
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='efc2no$eti$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).