Re: UI format

On Thu, 2003-09-25 at 13:48, Gerry Thompson wrote:
> Hi Barrie,
> 
> I had our UI guy have a quick peek at VCP and he has the following 
> suggestion:
> 
> When there are choices that must be typed in perhaps something like this 
> would convey more information and avoid typos:
> 
> Block of text describing the
> question, background,
> whatever.
> 
> 1. Choice A   Description of choice A
> 2. Choice B   Description of choice B
> 3. Choice C   Description of choice C
> ... etc.
> 
> Select choice (1,2,3)[Default, if any]:

Just checked in something like this without the "Description of choice
..." texts (though the default is indicated with a callout, look all
the way down for the example).  I'd like to allow first letter in
addition to number, but haven't got the time at the moment.

I'll be releasing an IPC::Run and an IPC::Run3 that work better on Win32
and don't have those nasty Socket::IPPROTO_TCP prototype mismatch
warnings, now that perl's been cleaned up a bit as well.

- Barrie

-----8<----------8<----------8<----------8<----------8<----------8<-----

C:\Perforce\VCP>perl -Ilib bin/vcp

This is vcp's text mode interactive user interface.  It asks a
series of questions and then allows you to save the answers in a
configuration file and/or do a conversion based on them.

After each question, multiple choice options or example free-form
input is shown in parentheses.  If a default value is available,
that is shown in square brackets.  You may press 'Enter' to accept
the default.

vcp may also be provided will all the information it needs on the
command line or using a configuration file.  To read up on these
options, run "vcp help" from the command line after quitting the
interactive interface.



    Enter the kind of repository to copy data from.

    1) cvs
    2) p4
    3) revml
    4) vss

Source SCM type? 1


    Enter the cvsroot spec.  Defaults to the CVSROOT environment variable
    if set.

cvsroot (cvsroot spec)?
*** Please enter a value.

cvsroot (cvsroot spec)? d:\CVSROOT


    Enter the cvs filespec.  This must be in the form "module/filespec".
    The filespec may contain trailing wildcards, like "a/b/..." to extract
    an entire directory tree.

cvs filespec (module/filepath/...)? foo/...


    Enter the CVS working directory (Optional). VCP::Source::cvs will cd
    to this directory before calling cvs, and won't initialize a CVS
    workspace of it's own (normally, VCP::Source::cvs does a "cvs
    checkout" in a temporary directory).

Enter CVS working directory? /tmp/foo/bah


    Warning: '/tmp/foo/bah' not found!

    1) no  <--default
    2) yes

Accept this value anyway [no]?