git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>, git@vger.kernel.org
Subject: Re: faster egit history page and a pure java "gitk"
Date: Tue, 25 Mar 2008 00:43:08 -0400	[thread overview]
Message-ID: <20080325044308.GA4759@spearce.org> (raw)
In-Reply-To: <47E7ADA3.2060906@intelinet.com.br>

"Roger C. Soares" <rogersoares@intelinet.com.br> wrote:
> Shawn O. Pearce escreveu:
> >OK, so I decided a few weeks back that the history page was not fast
> >enough.  I think I've spent the past 3 weeks writing true revision
> >machinary for jgit, and now connecting it up to a UI visualizer.
> >
> >  git://repo.or.cz/egit/spearce.git plotter
> >
> >The history page has been completely replaced.  I saw Roger has
> >some patches against the current history page.  :-|
> 
> Hi Shawn. This is awesome, I can't wait to see this integrated in the 
> main repo :)
> 
> I don't spend much time working on egit so I usually take a while to 
> make small things, but I can certainly merge my patches on top of yours.
> 
> Robin, how should I proceed, resend all my patches from the weekend on 
> top of Shawn's tree?

I just pushed a newer version out that contains support for showing
commits using a bold font if the commit has the highlightFlag set
on it.  I assume you were trying to work on a feature like gitk
has where you can type in a string and have gitk bold all of the
commits that contain that string in the message, right?

If you look at the newer internal.history.GitHistoryPage class there
is a historyFlag available as an instance member.  We also have an
SWTCommitList allocated in the inputSet() method.  The SWTCommitList
has an applyFlag method that accepts a RevFilter and adds the passed
RevFlag onto any commit that matches the filter.

There are a lot of RevFilter implementations, take a look at the
revwalk.filter package, or see the command line parsing code in
RevWalkTextBuiltin.  We have ones for author, committer, message...

So a good part of the code is there to do a bold/unbold thing.
There's also indexOf and lastIndexOf methods on SWTCommitList that
can search for the highlightFlag in either direction from a given
row index, making a prev/next feature pretty easy.

I decided to leave some low hanging fruit.  There's bigger and
more complex issues still lurking in the revwalk/treewalk features.

-- 
Shawn.

  parent reply	other threads:[~2008-03-25  4:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24  9:27 faster egit history page and a pure java "gitk" Shawn O. Pearce
2008-03-24 13:33 ` Roger C. Soares
2008-03-24 14:10   ` Robin Rosenberg
2008-03-25  4:43   ` Shawn O. Pearce [this message]
2008-03-25 12:33     ` Roger C. Soares
2008-03-24 14:06 ` Robin Rosenberg
2008-03-25  5:10   ` Shawn O. Pearce
2008-03-24 14:31 ` faster egit history page and a pure java "gitk" so Robin Rosenberg
2008-03-25  4:48   ` Shawn O. Pearce
2008-03-25  5:07 ` faster egit history page and a pure java "gitk" Roger C. Soares
2008-03-25  5:36   ` Shawn O. Pearce
2008-03-25  8:09     ` Shawn O. Pearce
2008-03-25 13:46     ` Roger C. Soares
2008-03-25 19:48       ` Robin Rosenberg
2008-03-26  1:37     ` Roger C. Soares
2008-03-26  4:52       ` Shawn O. Pearce

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=20080325044308.GA4759@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg@dewire.com \
    --cc=rogersoares@intelinet.com.br \
    /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).