On 02/15/10 20:11, Frank Schoenheit, Sun Microsystems Germany wrote:
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.
The intention behind the interaction handling mechanism is that interaction requests can be handled programmatically. Displaying something to the user is, in a sense, only a last resort activity of an interaction handler. Hence, interaction requests need to carry rich information to make it possible to meaningfully handle them programmatically.
-Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
