git/list[1] front-page[2] threads[3] people[4] search[5] about
 

gitk with hyperspace support

From
Paul Mackerras <paulus@samba.org>
Date
Aug 17, 2005, 00:21 UTC
Message-ID
<17154.33520.584666.701545@cargo.ozlabs.ibm.com>

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.

Next: Linus Torvalds
Message 1 of 13 in “gitk with hyperspace support”
  1. Paul MackerrasAug 17, 2005
  2. Linus TorvaldsAug 17, 2005
  3. Junio C HamanoAug 17, 2005
  4. SeanAug 17, 2005
  5. Matthias UrlichsAug 17, 2005
  6. Paul MackerrasAug 17, 2005
  7. Junio C HamanoAug 17, 2005
  8. Paul MackerrasAug 30, 2005
  9. Junio C HamanoAug 30, 2005
  10. Alex RiesenSep 1, 2005
  11. SeanSep 1, 2005
  12. Alex RiesenSep 2, 2005
  13. Matthias UrlichsAug 17, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.