On 12/6/02 8:13 AM, "Greg Stein" <gstein@lyra.org> wrote:
> On Tue, Jun 11, 2002 at 11:03:27PM -0700, Bill Tutt wrote:
>> Just to continue prodding this anthill called CollabNet employees, I
>> just realized that libsvn_client applications (i.e. UI apps) need
>> notification hooks that are currently handled via the "Force possibly
>> bad things to happen" Boolean that is (for example) passed into
>> svn_client_merge(), etc...
>
> whatthefuh? What "Boolean" are you referring to? You're being way too
> opaque.
>
> Yes, GUIs need notification hooks. The assumption is that the notify_func
> would be changed to be able to return a boolean indicating "stop". (but it
> won't return an error; that will make things way too complicated, and
> theoretically notification callbacks should not raise an eror)
>
>> i.e. A GUI is probably going to want to pop up a Yes/No dialog when
>> these situations occur.
>
> What situations? Clarity...
I'm thinking he's referring to --force switches. A GUI designer might not
want the user to have to specify --force in advance. Instead the app would
wait until an operation would fail without --force, and then pop up a dialog
box asking whether to force things. This means removing the boolean --force
parameters in the API and replacing them with some form of "I need to know
if I should force *this*" callback.
Of course, that's just my guess as to what Bill means...
The other option is for the gui to attempt the operation without --force and
if it fails ask if it should try again with --force.
\x/ill :-}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 12 17:40:57 2002