Re: [Subclipse-dev] History as revision graph

Thanks Mark.

The cache is calculated just once. But that first time it has to do
several calculations. For example when I get this log messege:

D /foo/bar

In my implementation I have to update all the subfiles and subfolders
of /foo/bar to mark them as deleted in that revision. However the
second time, the cache just needs to query for updates. For example in
a repository with 4000 revisions the first time it needs to cache
those 4000 revisions. But the next time the cache just will need to
cache 10, 20, 30 revisions. However, yes, for the first time it takes
too much time.

Now I'm using PreparedStatements and I reuse them. Maybe I could use
batch operations. But I'm not sure.

I want to take some metrics on different repositories. But I haven't
had time these days.

Also I would like to update the cache in chunks. For example from 100
to 100 revisions. By doing this I could update the monitor progress
bar between those chunks. Now I'm getting all the log messeges inside
one array by using

client.getLogMessages(info.getRepository(), latest, SVNRevision.HEAD);

Where "latest" is the latest revision number I have in the cache. Is
there any way to know which revision number has the HEAD revision?

On Thu, Jul 3, 2008 at 3:38 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> 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
>
>

-- 
Alberto Gimeno Brieba
Presidente y fundador de
Ribe Software S.L.
http://www.ribesoftware.com
ribe_at_ribesoftware.com
Contacto personal
eMail: gimenete_at_gmail.com
GTalk: gimenete_at_gmail.com
msn: gimenete_at_hotmail.com
página web: http://gimenete.net
teléfono móvil: +34 625 24 64 81
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org