Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Paul Mackerras <paulus@samba.org>,
	Brett Schwarz <brett_schwarz@yahoo.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Karl Hasselstr?m <kha@treskal.com>,
	Junio C Hamano <junkio@cox.net>, Carl Worth <cworth@cworth.org>,
	Michael Niedermayer <michaelni@gmx.at>,
	Git Mailing List <git@vger.kernel.org>
Subject: gitk and git-gui, was Re: FFmpeg considering GIT
Date: Tue, 8 May 2007 13:16:37 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705081311550.4167@racer.site> (raw)
In-Reply-To: <20070508041939.GK11311@spearce.org>

Hi,

On Tue, 8 May 2007, Shawn O. Pearce wrote:

> Paul Mackerras <paulus@samba.org> wrote:
>
> > Gitk ends up handling pretty significant amounts of data.  In 
> > particular the per-commit data can get to gigabytes, and processing it 
> > is pretty cpu-intensive.  I did try using namespaces for the 
> > per-commit data but I found that the performance hit to be more than I 
> > was willing to tolerate.
> 
> If that is the case then an obvious direction is to start using C for 
> the actual Git operations/datastore and Tcl/Tk for the basic UI layout 
> and event handlers.

It might be a much better idea to write something a la git-fetch--tool, 
which is a helper in C (thus very fast and memory efficient), outputting 
easily parseable data. 

For example, when constructing the commit graph, the calculations could be 
done in C, and Tcl/Tk could do _just_ the display. AFAIK tig already has 
the algorithm implemented in C...

The big benefits would not only be that you can compile this without the 
headers/libs of Tcl/Tk (possibly avoiding the problem we experienced when 
trying to compile Git with gcc, and linking to Perl, which was compiled 
with a different compiler), but other Git viewers could take this output 
as well, avoiding reimplementing the algorithm in Ruby or Haskell.

Ciao,
Dscho

  reply	other threads:[~2007-05-08 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  3:39 FFmpeg considering GIT Brett Schwarz
2007-05-08  4:06 ` Paul Mackerras
2007-05-08  4:19   ` Shawn O. Pearce
2007-05-08 11:16     ` Johannes Schindelin [this message]
2007-05-08 15:33       ` gitk and git-gui, was " 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=Pine.LNX.4.64.0705081311550.4167@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=brett_schwarz@yahoo.com \
    --cc=cworth@cworth.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=kha@treskal.com \
    --cc=michaelni@gmx.at \
    --cc=paulus@samba.org \
    --cc=spearce@spearce.org \
    --cc=torvalds@linux-foundation.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