[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] cvn resource history view

From: Eugene Kuleshov <eu_at_javatx.com>
Date: 2005-07-25 18:15:08 CEST

Mark,

   I've created a cumulative patch with all the enhancments
   http://subclipse.tigris.org/issues/show_bug.cgi?id=349

   So far not very advanced actions, mostly exposing existing ones for
different selection.

   As I mentioned before there could be some glitches (pefrormance
issues) on affected patch pop-up menu. But I can't reproduce itwith a
local server. So, here it is for now.

   I'll be able to look at this once I'll get back from my vacation, so
I will be able to run some tests with remote repositories.

   regards,
   Eugene

Mark Phippard wrote:
> Eugene Kuleshov <eu@javatx.com> wrote on 07/19/2005 10:38:46 AM:
>
>
>> I wonder if it worth to implement few additiona loptions for SVN
>>resource history panel. I was thinking of the following:
>>
>>-- Option to wrap commit comments in comment text panel. See similar
>>chage for CVS at https://bugs.eclipse.org/bugs/show_bug.cgi?id=104129
>
>
> Sounds good
>
>
>>-- Option to hide text comment panel and/or affected paths panel
>
>
> Yes
>
>
>>-- Option to stack affected path and comment text areas vertically -
>>vertical, horisontal and auto (similar to the way it is done in JUnit
>>view and few others; basically when view is narrow and high it uses
>>vertical layout)
>
>
> Yes
>
>
>> I still looking at menu and comparison actions for affected paths...
>
>
> I definitely think the UI of this view could be better. These are all
> good ideas. I would like to see us add some ability to limit the number
> of messages so as to improve performance. The new log --limit feature
> could do this. Unfortunately, it works real bad against a 1.1 server,
> which is what tigris.org is running, so it should be optional to use it.
>
> We should also expose the --stop-on-copy option.
>
> Finally, what TortoiseSVN used to do, before the new --limit option, was
> figure out that the last changed revision for the selected item was N and
> then run the command:
>
> svn log -r N-100:N url://
>
> This gives all of the log messages in the last 100 revision. The nice
> thing is that it runs fast on all servers. The bad thing is that you
> might only get 1 revision in that range.
>
> Mark
>
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
> _____________________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
Received on Tue Jul 26 02:15:08 2005

This is an archived mail posted to the Subclipse Dev mailing list.