Mark Phippard wrote:
> No, sharing a project creates a folder for the project in the repository
> and then checks it out. That puts the folder at r1. Now you commit files
> in r2. The folder is still at r1.
Why is it still at r1? So after sharing a project and adding and commit
files in it, part of my project is at r2 and part of my project is at
r1? That is somehow inconvenient. If I share a project through the Share
Project wizard and commit files as part of this process then I would
expect to continue any operation after that without any error message.
Mark, you see my point? It is the user experience that needs improving
here. It might be 100% correct behavior technically (from a Subversion
WC perspective) but it is incorrect (or at least inconvenient) behavior
for an end-users. As an end-user I don't want to deal with output in the
console and error messages in the console.
Here is another usability example, which may sound awkward to
experienced Subversion/ClearCase users. ClearCase Snapshot views are a
little bit like WC. You have a snapshot there. But ClearCase actually
has that concept of check-outs. You need to checkout a file before you
can edit it, otherwise it's read-only. But then you did the check-out in
a Snapshot view, only that version was checked out, that you have in
your view. That means, it was probably not LATEST. Because some users
never understand that behavior or developed a sensitivity for it, admins
ended up writing client hooks for this. And I ended up implementing a
preferences in the ClearCase plug-in to support (mimic) this behavior.
Cu, Gunnar
--
Gunnar Wagenknecht
gunnar@wagenknecht.org
http://wagenknecht.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jul 28 21:20:28 2006