1.5.0-RC3: Repo-browser collapses tree nodes automatically

Hi,

I would like other users to ask about the new behaviour of
automatically collapsing tree nodes in the repo browser. Please see
the following mail transcript below from Scott, Stefan and myself.
What do you think about this ?

>> > After any operation done directly in the repo browse (ie., create
>> > folder), all trees are collapsed closed. Combined with the 'slowness'
>> > issue of drilling down, it becomes a bit painful.

> That's because after most operations, the content is not known anymore and it must be refreshed. >For example, if you create a folder then the HEAD revision changes, and that means we must refresh >the folders.
> Because the repobrowser can't know whether there was another commit from another user >happening in between the first start and the change of the HEAD revision.

can we make this optional (collapsing the tree ?). My reason to stay
with the old behaviour is:
- lots of people are used to the old behaviour. I think you will get
lots of questions
- collapsing tree nodes automagically is not so intuitive. (lets say I
find it irritating)
- as scott says, combined with the slowsness, it be comes even more
painfull.
- the common usecase (80%) is i think, that the repo structure does
NOT changes so often.
esp. during browsing, so I would more like a error msg that my command
did not succeed in the remaining 20%, than to have a slow browsing and
navigation behaviour in the 80% ;-)

hope this makes sense,

thanks,
Bernhard.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-18 16:52:05 CEST