Add an interactive wizard of some kind to greatly simplify
setup of a P4Transfer configuration.
It should query the user for a working directory (the root
of the workspaces and home of the transfer.cfg file), and
then query them for details of the source and target servers.
It should then ask questions that determine the set of default
flags to be used for that configuration (e.g. -k, --ignore,
etc.), and somehow persist that information, e.g. perhaps
generating a 'P4TransferWrapper.py' wrapper script that
just calls P4Transfer.py withose flags.
Then the wizard should generate the workspaces to be used
with P4Transfer on both the source and target servers. It
should login in using the credentials provided (relying on a
ticket if no password is specified, just as with normal
P4Transfer.py operation).
The workspaces should be configured with best practices for a
workspace used P4Transfer. By "best practices," it should,
for example, determine whether 'noallwrite' or 'allwrite'
option and/or the submitunchanged/leaveunchanged option is best
for a workspace to be used with P4Transfer. If there is no
best practice, just pick one.