Rickard Oberg <[EMAIL PROTECTED]> wrote:
>Justin Forder wrote:
>> My guess is that the GUI is not intrinsically hard, it's just not a
>> style of interaction that is currently supported in EJX. To make it less
>> dangerous, there should be a "restore default settings" button (or the
>> user defines new configurations, and chooses between them, with the
>> original configuration always being available as a choice).
>
>Yes, that's how it should be (perhaps; I still think that it's a bit of
>a usability problem). In the meantime I think I'll go with the easier
>GUI (all settings in one place) and keep it fixed.
I was taking "usability" to relate to the question: "I know what I want
to do; can I understand how to use this tool to do it?", and I was
assuming that (for example) Add... and Remove buttons together with
drag-and-drop ordering would be OK for this.
A more ambitious interpretation of "usability" would relate to the
question: "can I use this tool to explore configuration alternatives in
safety?"
Satisfying this would require constraints (e.g. preconditions and
postconditions) to be associated with interceptors, and all changes in
the tool to be checked against these constraints. Too ambitious?
Stepping back, the question we should ask first is: "Who needs this
facility?"
My answer: Interceptor developers.
They may have a different toolset from end-users/sysadmins, and I feel
that they would benefit from the GUI tool (or the config file).
--
Justin Forder
