Kate Rhodes wrote:
b) I agree with frank about not wanting swixml to start including any
scripting functionality. I like that it's just basic GUI.
Just a quick reply to this part: I am not really talking about
scripting here, beyond some simple-ish enabling and disabling of components.
Let me try an example XML snippet:
<events>
<event onComponent="componentID" when="true" enables="comp1,comp3"
disables="comp2"/>
<event onComponent="componentID" when="false" enables="comp2"
disables="comp1,comp3"/>
</events>
In this case, suppose componentID points to a checkBox. When it is
selected, is enables some components and disables others. It does the
reverse when it is unselected.
I don't know, it may be too unwieldy to be useful. It's just a thought.
c) why couldn't we have something like action="windowAction"
actionType="java.awt.event.WindowListener"
If I understand what you are getting at, you want a way to be able to
associate listeners of other types in the way we do ActionListeners. I
think this may be a good idea, if we can come up with some good syntax.
That would certainly answer the concerns of those who want more
flexibility.
Pat.
