git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: git@vger.kernel.org
Subject: gitk with hyperspace support
Date: Wed, 17 Aug 2005 10:21:04 +1000	[thread overview]
Message-ID: <17154.33520.584666.701545@cargo.ozlabs.ibm.com> (raw)

I have been trying a new approach to drawing the commit graph in gitk.
This involves sending a lot of the really long lines into
"hyperspace", by terminating them with an arrow pointing down when the
graph gets too wide, and then reintroducing them later with an arrow
pointing up, as though they had used a warp drive to dive beneath the
screen (into the mysterious 3rd dimension :) and then reappear later.
The result is that the graph stays at a reasonable width and doesn't
need to be compressed.

My reasoning is that it is the local short-range connections which are
interesting and informative.  The long-range connections aren't really
visually informative; if you want to know about the long-range
connections, the parent and child lists in the details pane are much
more useful.

I would like to get some feedback about what people think of the
visual effect of this new approach, and in particular whether having
the lines jump into hyperspace loses information that people find
useful.  The new version is at:

http://ozlabs.org/~paulus/gitk/gitk.hs

If the reaction is positive I'll check this into my gitk.git
repository.

Thanks,
Paul.

             reply	other threads:[~2005-08-17  0:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17  0:21 Paul Mackerras [this message]
2005-08-17  3:02 ` gitk with hyperspace support Linus Torvalds
2005-08-17  6:58 ` Junio C Hamano
2005-08-17  8:13   ` Sean
2005-08-17 15:56     ` Matthias Urlichs
2005-08-17  9:57   ` Paul Mackerras
2005-08-17 22:34     ` Junio C Hamano
2005-08-30  1:46   ` Paul Mackerras
2005-08-30  7:50     ` Junio C Hamano
2005-09-01 20:10     ` Alex Riesen
2005-09-01 21:26       ` Sean
2005-09-02 13:20         ` Alex Riesen
2005-08-17 14:37 ` Matthias Urlichs

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17154.33520.584666.701545@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).