Hi,
Perhaps I'm getting something wrong in the interaction handler API, but
in my understanding, what this API (or the current implementation) is
missing is some kind of "generic" request. That is, when I want to show
some arbitrary string to the user, together with a set of
yes/no/cancel/retry/OK buttons (defined by myself), then there's no way
to do this with the standard css.task.InteractionHandler implementation.
While it has an impressive list of requests it can handle (and the
documentation is not even up-to-date), all those requests are pretty
specialized.
In the most simple form, the functionality I have in mind would just be
giving the interaction handler implementation the responsibility for
arbitrary ClassifiedInteractionRequests. That is, after finding that the
request is not of a known/handled type, then at least do the generic
handling if it is a ClassifiedInteractionRequests: Take the Message
string, open a message box with buttons according to the available
continuations, and display that.
Well, for those saying that Exception.Message is not for being displayed
to the end-user, let's have a
exception GenericInteractionRequest : ClassifiedInteractionRequest
{
string DisplayMessage;
}
I'd happily implement this, but I'm interested in opinions why we don't
have this, yet - does it somehow contradict the intention of the
interaction handler, and I just do not grasp it? Or did just nobody ever
bother?
Opinions?
Thanks & Ciao
Frank
--
- Frank Schönheit, Software Engineer [email protected] -
- Sun Microsystems http://www.sun.com/staroffice -
- OpenOffice.org Base http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
