We are working hard on finalizing the Swixml 1.0 api. I'm pushing this because we have introduced quite a few new things during the last 4 or 5 weeks but also removed a couple features and we all know how important is to work with a stable api. To continue my work on Franklin the XML GUI Editor for Swixml. Here are two old screenshots: http://www.carlsbadcubes.com/franklin/ I need a stable API myself ;-)
Moreover, I'm not entirely convinced yet about the whole listener idea. Doing a lot of swixml programming myself, I don't really follow a purist approach. Whenever I think that something is easier done through Java code then through an XML descriptor I consider doing it through code - depends on other factors as well of course. However, just because one can imagine that it can be done through XML doesn't mean we have to do it. Again, please keep in mind what we intended swixml to be (or I should say to become). Wolf > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Frank Meissner > Sent: Saturday, March 08, 2003 1:55 PM > To: [email protected] > Subject: [Forum] Re: syntax for populating listy things > > > Hi, > > I'd like to say something on the listener topic masukomi mentioned here. > > I think he is wrong with his opinion with Actions meryly acting as > ActionListeners. > > Actions in the context of JMenuItem, JButton, (in fact, all descendants > of AbstractButton) define the name, the icon, the tooltip, the shortcut > keys, the mnemonic of the AbstractButton (ie JMenuItem, ...). So, if you > create e.g. a JMenuItem from a Action, you do not neet to specify Text, > Mnemonic and the like for your MenuItem. All this is provided by the > Action object you give to JMenuItem(Action). > > So, you are able to write a complete application with menus, toolboxes, > buttons and whatever without calling any other constructor for > JMenuItem, JButton,... than the one with a single Action argument. As I > stated out earlier, I just did that a couple of month ago. In the whole > application where only about 5 (some old left-over or just too simple to > convert them) of menu items not constructed from action objects -- and > about 50 actions besides this... These actions where able to change > their texts according to the current locale because they registered > themself on some locale provider and kept their "enabled" state > according to some data source in the application. Because I'm very fond > of this, I dare say there is no _need_ of any other constructor for > jmenuitem than the one with a action argument. Of course, then there is > no need to explicitly set the text, mnemonic ant tooltip for the > jmenuitem as well... Change the appropriate attributes of the action > object and you are done. The text, tooltip (a bug still in jdk 1.4.1_01 > prevents the tooltip from working correctly though), mnemonic, icon > (...) of all AbstractButtons (constructed by the action) in your > application will change accordingly... But this is my very > personal opinion. > > I agree with the listener idea, but would also like to have a custom > creation there (like the one I implemented for direct constructor > arguments like Action for AbstractButton). What about e.g. > treeExpansionListenerInitType="com.fancycompany.control.FancyTreeE > xpansionListner"? > > Please do not remove the Action attribute! > > > Frank > > > _______________________________________________ > Forum mailing list > [email protected] > http://mars.lunarpages.com/mailman/listinfo/forum_carlsbadcubes.com > >
