At this point I would rather not put event definitions into the XML-descriptors. Like pointed out on the swixml.org site: "SWIXML does Java Swing GUI generation and that is all. The dynamic behavior of the user interface, defining the application's business rules, has to be coded in Java."
I don't want to dismiss a new ideas but I think we have to draw a line somewhere. Therefore, I'm not going to support anything that introduces scripting behavior into XML-descriptors. And don't foul yourself, when="true", when="false", .. is scripting. Not that I'd think that this is a bad idea all together but there are already projects available doing those kind of things. Like I have states before, swixml is not a GUI tool for everything and certainly not for everybody. SWIXML differentiates itself from other comparable tools (like Thinlet, XUL, XULUX, Swang, SwingML, etc.) by focusing completely on javax.swing. Programmers who know Swing already can immediately start writing descriptors. No additional XML dialect has to be learned: Class names translate into tag names and method names into attribute names. SWIXML is faster since no additional layers had to be added on top of the Swing objects. SWIXML is smaller. Despite the fact that the SWIXML jar file is only about 36 Kbyte in size, almost all of the infamous Swing objects are supported. SWIXML does Java Swing GUI generation and that is all. The dynamic behavior of the user interface, defining the application's business rules, has to be coded in Java. -- Wolf Paulus C a r l s b a d C u b e s mailto:[EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Patrick Forhan > Sent: Friday, March 07, 2003 9:14 AM > To: [email protected] > Subject: Re: [Forum] Events and Models > > > 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. > > > _______________________________________________ > Forum mailing list > [email protected] > http://mars.lunarpages.com/mailman/listinfo/forum_carlsbadcubes.com > >
