Re: Re: Suggestion for improved use of cvs checkout to update sandboxes

> It works by simply storing the mapping of directory paths against the
> module or cvsroot when doing the checkout to be used when the next
> checkout for the same selection is done. Searching for a match in the
> stored dictionary is progressive up the folders hierarchy so even if
> subfolder deep down the tree is selected the match for the parent will
> be found.

Looks good. However, here's a slightly related observation:
When invoking the Module browser the CVSROOT settings from the parent dialog
are not transfered to it and have to be entered anew. This is a bit
annoying.


> I stopped short of implementing the "Skip dialog" feature for checkout
> however, at least for now. It seems to be more safe to just offer
> stored values as defaults so all the user has to do is to press Enter
> key to confirm. It's much better than before when module name and
> cvsroot had to be entered each time. We can optimize implementation
> before adding the skip option.

One more: I've got several sandboxes that represent non-root-level modules,
i.e. I usually check them out using the -d option (aka "checkout into
directory"). This is currently not being remembered as part of the mechanism
but probably should be if you are going to make the Checkout dialog
skippable... OTOH, those are obviously non-"virtual" modules, so I could
just as well use update -d on those...

And yet another one: While we're at it it'd be nice if we could come up with
some way to check out multiple modules at once as is possible from the
commandline. Maybe simply allowing space separated module names is feasible?
The module browser might have to get an additional button or some other way
to specify whether I wish to add the selected module to the list of existing
ones or whether I want to replace the existing entry (current behaviour).


> Please take a look and - as always - comments and suggestions are
> welcome!

Task fulfilled I guess... ;)

Cheers,

Oliver
------
In everybody's best interest, please do not post or CC technical questions
to me in private unless they are specifically about a macro/product of mine
that is NOT already bundled with WinCvs. I will generally forward my replies
to such posts to the CVSGUI list without further notice.
----  ------------------
JID:  [email protected]
ICQ:  18777742     (http://wwp.icq.com/18777742)



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/