Sparse Working Copy Checkout Personal Evaluation, kudo and complaint

See comments inserted below.
 
From: Stefan Küng <tortoisesvn_at_... <http://gmane.org/get-address.php?address=tortoisesvn%2dRe5JQEeQqe8AvxtiuMwx3w%40public.gmane.org> >
Subject: Re: Sparse Working Copy Checkout Personal Evaluation, kudo and complaint <http://news.gmane.org/find-root.php?message_id=%3c4760293E.8010200%40gmail.com%3e>
Newsgroups: gmane.comp.version-control.subversion.tortoisesvn.user <http://news.gmane.org/gmane.comp.version-control.subversion.tortoisesvn.user>
Date: 2007-12-12 18:32:30 GMT (3 hours and 45 minutes ago)

Mark Swann wrote:

> I was particularly interested in how TortoiseSVN facilitates the new
> Sparse Working Copy Checkout, so I performed a few experiments and came
> to the following conclusions:
>
> (1) The process is way too tedious, especially if the directory you are
> checking out is nested multiple directories deep. You have to check out
> each ancestor directory one at a tedious time until you finally reach
> the directory you really want. The Repo Browser Context Menu needs to
> allow the "Update item to revision" option on any directory that has a
> near or distant ancestor that is already checked out, and Tortoise
> should checkout out all intermediate ancestors automatically.

Implemented the creation of intermediate directories in revision 11591.

> (2) The normal procedure for checking in your changes should be to first
> perform an Update, then a Commit. OOPS! Not with a sparse working copy,
> you don't! If you make the mistake of doing what is intuitive (an
> Update), you will suddenly find your working copy is no longer so
> sparse. This feature is way bad. I don't know if this reflects SVN's
> intentions but you should never add a feature that makes it easier for
> the user to make a mistake. I don't care if you have provided an
> alternative proper way to do the update, which is also very tedious, you
> should make the sparseness of the working copy transparent to normal
> daily use, i.e. you must allow the normal Update/Commit procedure
> without retrieving all the un-checked-out files in the tree.

As Simon already mentioned: we don't need a lecture in UI design and/or
how to make an application user friendly. A simple recipe on how to
reproduce the problem would be much better.
Anyway: you've discovered a bug which I fixed in revision 11590.
Frankly, I have long ago stopped apologizing for my style. I "lecture", as you call it, because I have found it better to say more now, so I can say less later. It saves time and misunderstanding.
I really appreciate you prompt response and quick fix, but I think you are showing a bit of arrogance to imply that you know all there is to know about creating a user friendly application.

Please try the next nightly build.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net <http://tortoisesvn.net/>