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

Re: [TSVN] RFE: Lock_and_open as a single command

From: Kalin KOZHUHAROV <kalin_at_thinrope.net>
Date: 2005-09-07 17:59:02 CEST

Simon Large wrote:
> Kalin KOZHUHAROV wrote:
>
>> Milen A. Radev wrote:
>>
>>> On 07/09/05, Kalin KOZHUHAROV <kalin@thinrope.net> wrote:
>>>
>>>> Hi again.
>>>>
>>>> Today I just found out myself working with a lot of Word files set
>>>> with svn:needs-lock...
>>>> The algorithm is:
>>>> right-click, get lock, don't write MSG, press OK, wait, press OK,
>>>> double-click
>>>
>>>
>>>
>>>
>>> You could select several files (in a folder) at once and "Get Lock..."
>>> for all of them.
>>
>>
>> Yes, but a have to edit them one after another usually, with other
>> devs writing in between. That is why we divided a huge single file
>> into several small ones at first place.
>
>
> So your method of working is:
>
> repeat
> lock 1 file
> open/edit/save file
> commit 1 file
> until TimeToGoHome

Well kind of. The only thing not predictable is the order of the
files updating. It is dynamic (chaotic?), as everybody is working on
different parts (at different times) on one file, one-two files at a
time per person. I hate the " -two" part, but there are related
files (thunk copy-paste :-( and integrating more word files into a
single master document turns to be more pain than gain.

Why do we use Word for this things? A good question with a good
answer - it is required as a final product in most any (Japanese)
big company. After I finish with this project, I am to try and think
of better idea {(something like use text/XML files that get together
and pretty print to a final document. (is there such a thing when
you output Word :( And yes, I have asked every customer till now,
"Don't you prefer XML and PDF?" Guess the answer...}

> > Suggest command name "lock && open" :-)
>
> I was going to suggest "open with lock" ;-)

Well, I am sticking with my suggestion :-) More intuitive as this is
  how goes in practice. "lockopen" is anther thing, "lock open",
"lock_open", "lock_edit" ...

What about simply "edit" and a pref that says "Before edit, lock
files that need locking"...

Drilling further, change the default open command for files with
svn:needs-lock and add command "open [readonly]", make that a pref.

Ooops, time to go to bed...

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 7 18:00:13 2005

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