git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Roger C. Soares" <rogersoares@intelinet.com.br>
To: "Shawn O. Pearce" <spearce@spearce.org>
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 02:07:42 -0300	[thread overview]
Message-ID: <47E8889E.6090403@intelinet.com.br> (raw)
In-Reply-To: <20080324092726.GQ8410@spearce.org>

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 Guys,

I saw it running now, here are my initial comments/impressions:

I have a git.git clone on my eclipse and now egit can open it, cool! :) 
But it wasn't that fast, it took some minutes to finish building the 
whole tree. Also, changing projects (different git repos) makes the cpu 
go very high, and what opened fast the first time takes minutes after...

When reading the email I thought the new history page would have the 
same features from the current, but it doesn't. It looks promissing thought.

My first impression is that I like the current way of showing files in 
the strutucture compare better. In the future I would like the option to 
make it open on the left pane (where package explorer is) and have the 
options to collapse/expand directories, present in flat/hierarchical 
modes, have the fast view, etc.

Comments now can't be automatically wrapped. I actually prefer to leave 
wrapping to the computer, I don't like having to manually fix line 
lenghts when amending a comment, I think eclipse should do it. Also, 
currently, the history page usually has little space allocated for it 
and currently the first lines of the comment are visible. In the new 
page I have to scroll to see the comment when the history page is not 
maximized.

[]s,
Roger.

  parent reply	other threads:[~2008-03-25  5:11 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
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 ` Roger C. Soares [this message]
2008-03-25  5:36   ` faster egit history page and a pure java "gitk" 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=47E8889E.6090403@intelinet.com.br \
    --to=rogersoares@intelinet.com.br \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg@dewire.com \
    --cc=spearce@spearce.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).