Hi,
right now, subversion has one typedef for clients to
prompt the user for information like username and
password. This callback is used even for question
like prompts ("accept certificate y/n").
I suggest changing the existing typedef or adding
some more:
typedef svn_error_t*(* svn_client_prompt_t)(const char **info, const char
*prompt, svn_boolean_t hide, void *baton, apr_pool_t *pool)
typedef svn_error_t*(* svn_client_prompt_t)(const char **username, const
char *promptusername, const char **password, const char * promptpassword,
svn_boolean_t *store_auth_info, void *baton, apr_pool_t *pool)
with that provider a GUI client could prompt for username/password in _one_
dialog and also have a checkbox where the user can check if (s)he want's to
store the authentication info or not (for that particular operation).
typedef svn_error_t*(* svn_client_prompt_t)(const char *prompt,
svn_boolean_t * answer, void *baton, apr_pool_t *pool)
with such a provider subversion could ask questions like "accept ssl
certificate?" and the client then can itself either
add strings like (y/n) or buttons to the dialog - the answer (yes/no) would
get returned to subversion as a boolean value.
right now GUI clients show a dialog box with the question and the user then
enters 'y' or 'n' into an editbox. This looks ugly 'cause the user is used
to just 'click' yes or no and not used to enter 'y' or 'n'. Sure the client
could provide that by simply returning 'y' if the user clicks the
yes-button, but that would mean hard-coding the answer and it will break as
soon as subversion supports multiple languages.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 1 20:06:13 2003