> What's with the quotes and the dumbing.. Trying to convince this old
> idiot that Unlock is a good name by enclosing it in ""s? :-)
You seem to be under the impression that I have somehow addressed these
messages to you or about you. I see you have posted a lot of messages on
this topic, but I haven't read them all. I was simply explaining MY design
idea to Stefan. My comments are independent of any other messages. Sorry
for the idiot comment, it was not referring to anyone on this list. It was
in the spirit of trying to design the UI as if the users know nothing and
we have to walk them through every scenario and choice via the UI. My
point was that if the users do not know what they are doing, making it easy
to steal each others locks is probably the worst way to approach this.
I put "Unlock" in quotes to emphasize that I was suggesting the user would
use the "Unlock" option on the menu. I had explained that in the previous
message but your reply said I was suggesting to use the CLI, which I was
not. I was trying to emphasize the UI option I was referring to when I
said Unlock. I think you got confused because I mentioned the command line
option that I was proposingthe UI invoke (svn unlock --force). I was not
suggesting anyone use the CLI.
> I'm not sure where you propose that this checkbox be placed.
> In a dialog presented _before_ the unlocking takes place?
I assume Lock will be a lot like commit. You will select some files, and
get a dialog a lot like commit where you can enter your lock comment and
press OK or Cancel. Likewise, I assume Unlock will be a bit like Revert.
You will get a confirmation dialog with selected files. I am proposing the
Check box live on that dialog.
>> I just think the UI should be clean and simple.
> Of course, we all do.
Many of your suggestions seem to be at odds with that statement. I have
seen little that is clean and simple proposed by you. Perhaps you just are
not expressing your ideas as clearly as you see them in your head though.
>> Stefan is already adding an unlock option to the product, we should just
>...And shut up with the suggestions for now, or what's your point with
>the above statement?
Again, I am simply stating MY suggestions for how the UI ought to work. I
am not sure why you interpret that as me telling you to shut up. Should
only your suggestions be put forth and discussed? Everyone, including
Stefan, are free to just discard my suggestions if they choose. I am just
trying to answer Stefan's original email and clarify how I think this ought
to work. Nothing more, nothing less.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 10 13:19:20 2005