On Thu, Jul 3, 2008 at 9:30 AM, Alberto Gimeno <gimenete_at_gmail.com> wrote:
> Ok. I didn't see any advantage in implementing it as an Editor. Now I
> see: we can have several instances, each one showing a different
> graph.
>
> So, I have just commited the changes I've made to make it work as an
> editor. So now I don't listen to selection changes. And I have moved
> the popup menu action to the "team" group.
>
> Now I want to work in the graph.
> * Zomm in / out
> * Outline
> * Nicer (I like something like this http://trac-hacks.org/wiki/RevtreePlugin).
> - different colors and maybe shapes (circle, rectangle,...) for each branch.
> - less information in each node. For example only show the revision
> number. But you'll be able to see that information maybe as a big
> tooltip when moving the mouse over the node.
> - different colors and maybe shapes depending on the action ('A', 'M', 'D').
> - highlight the selected branch.
>
> I'll think on how to add the merge information to the database.
Thanks. It is all looking good.
I think one of the big improvements would be figuring out information
you could not show, or at least optionally hide.
The cache seems to be working well. It seems a little slow to build
it though. I wonder if Derby is a bottleneck at all? For example,
could bulk inserts be used instead of adding one row at a time?
I wonder if there is some cache management we could add as well? I
assume we associate the cache with a repository, so perhaps in the SVN
Repositories view we could add some options for maintaining the cache.
It might be cool if I could build the cache for an entire repository
and just pay the price once.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-07-03 15:38:33 CEST