Comments on: Swing Action configuration goodness http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/ Sam Newman's blog Sat, 05 Jul 2008 00:46:27 +0000 http://wordpress.org/?v=2.5.1 By: Damien Bonvillain http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-215 Damien Bonvillain Wed, 25 Feb 2004 19:13:16 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-215 We lose the hierarchical vision with a flat format, but compared with XML as a (twisted) tree-model, there's less fluff. And the structure for a menu is generally 2-levels deep at most. In 1999, YAML didn't exist, but it's interesting to see a specification for this. We lose the hierarchical vision with a flat format, but compared with XML as a (twisted) tree-model, there’s less fluff. And the structure for a menu is generally 2-levels deep at most. In 1999, YAML didn’t exist, but it’s interesting to see a specification for this.

]]> By: Sam Newman http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-214 Sam Newman Tue, 24 Feb 2004 13:30:07 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-214 More readable? Perhaps, but you are displaying fundamentally hirearchical data in a flat format. A nice compomise might be to use something like YAML (http://www.yaml.org/), which I would consider if there was a mature parser out there. YAML looks like this: invoice: 34843 date : 2001-01-23 bill-to: &id001 given : Chris family : Dumars address: lines: | 458 Walkman Dr. Suite #292 city : Royal Oak state : MI postal : 48046 Whitespace is used to define grouping as opposed to wrapping everything with tags. More readable? Perhaps, but you are displaying fundamentally hirearchical data in a flat format. A nice compomise might be to use something like YAML (http://www.yaml.org/), which I would consider if there was a mature parser out there. YAML looks like this:

invoice: 34843
date : 2001-01-23
bill-to: &id001

given : Chris
family : Dumars
address:
lines: |
458 Walkman Dr.
Suite #292
city : Royal Oak
state : MI
postal : 48046

Whitespace is used to define grouping as opposed to wrapping everything with tags.

]]> By: Damien Bonvillain http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-213 Damien Bonvillain Tue, 24 Feb 2004 12:40:05 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-213 Doing all this with property files is doable (and perhaps more readable), but the handling should take care of rebuilding a tree. I've a project from 1999 which does this. Here is a sample of one of the property files : # Toolbar définition toolbar= rt - il routage rtLabel=Routage rtTooltip=Modifie le routage ilLabel=Ilot routageTooltip=Ajouter une gamme routageImage=new1.gif # Statusbar definition statebar=un deux trois quatre cinq six sept unLabel= Route deuxLabel=Modif troisLabel=Erreur quatreLabel=(x,y) cinqLabel=nb_mac sixLabel=nb_seg septLabel=v_flux # Actions behaviour modifiers= creer efface_mac creerTooltip=Créer une machine creerNec=RIEN NO_MAC NO_FLUX creerRej=DROIT CTRL creerNecAide=RIEN NO_MAC NO_FLUX creerRejAide=CTRL efface_macTooltip=Effacer la machine efface_macNec=RIEN DROIT CTRL efface_macRej=NO_MAC efface_macNecAide=RIEN CTRL efface_macRejAide=NO_MAC The last section is conditions for an Action to be applicable, described as a set of necessary (Nec) conditions, and a set of vetoed conditions (Rej). Conditions refer to the UI (CTRL, DROIT refer to the mouse) or to the domain model (NO_MAC, NO_FLUX, RIEN). Doing all this with property files is doable (and perhaps more readable), but the handling should take care of rebuilding a tree. I’ve a project from 1999 which does this. Here is a sample of one of the property files :

  1. Toolbar définition
    toolbar= rt – il routage
    rtLabel=Routage
    rtTooltip=Modifie le routage
    ilLabel=Ilot
    routageTooltip=Ajouter une gamme
    routageImage=new1.gif

  2. Statusbar definition
    statebar=un deux trois quatre cinq six sept
    unLabel= Route
    deuxLabel=Modif
    troisLabel=Erreur
    quatreLabel=(x,y)
    cinqLabel=nb_mac
    sixLabel=nb_seg
    septLabel=v_flux

  3. Actions behaviour
    modifiers= creer efface_mac
    creerTooltip=Créer une machine
    creerNec=RIEN NO_MAC NO_FLUX
    creerRej=DROIT CTRL
    creerNecAide=RIEN NO_MAC NO_FLUX
    creerRejAide=CTRL
    efface_macTooltip=Effacer la machine
    efface_macNec=RIEN DROIT CTRL
    efface_macRej=NO_MAC
    efface_macNecAide=RIEN CTRL
    efface_macRejAide=NO_MAC

    The last section is conditions for an Action to be applicable, described as a set of necessary (Nec) conditions, and a set of vetoed conditions (Rej). Conditions refer to the UI (CTRL, DROIT refer to the mouse) or to the domain model (NO_MAC, NO_FLUX, RIEN).

]]> By: Sam http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-212 Sam Mon, 23 Feb 2004 18:34:25 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-212 I'm not sure I agree. I'm not just setting the display name of the action here - I'm also defining an icon, keyboard shortcut, mnemonic, and logical grouping (e.g. menu x has these actions). You can do all that with property files? Property files work greate for flat simple string data - but for more compelx datatypes and hirearchical structure, XML is a better choice IMHO. I’m not sure I agree. I’m not just setting the display name of the action here – I’m also defining an icon, keyboard shortcut, mnemonic, and logical grouping (e.g. menu x has these actions). You can do all that with property files? Property files work greate for flat simple string data – but for more compelx datatypes and hirearchical structure, XML is a better choice IMHO.

]]> By: Neil Weber http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-211 Neil Weber Mon, 23 Feb 2004 17:44:18 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-211 I use standard .properties files for this same stuff. Then just use ResourceBundle to locate the locale-appropriate .properties file. Using XML here is way overkill. It's always surprised me that Swing doesn't have built in support for ResourceBundles. Making every developer create their own i18n solution is just wrong. I use standard .properties files for this same stuff. Then just use ResourceBundle to locate the locale-appropriate .properties file. Using XML here is way overkill.

It’s always surprised me that Swing doesn’t have built in support for ResourceBundles. Making every developer create their own i18n solution is just wrong.

]]> By: Sam Newman http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-210 Sam Newman Mon, 23 Feb 2004 15:40:17 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-210 Do you have to configure your actions multiple times under each namespace? Do you have to configure your actions multiple times under each namespace?

]]> By: Jason Carreira http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-209 Jason Carreira Mon, 23 Feb 2004 15:31:15 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-209 I think your different roles / functions are the answer to how to use XWork namespaces... We use them in WebWork to map paths, which can be used for declarative security. I think your different roles / functions are the answer to how to use XWork namespaces… We use them in WebWork to map paths, which can be used for declarative security.

]]> By: Sam Newman http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-208 Sam Newman Mon, 23 Feb 2004 12:58:44 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-208 Firstly, for internationalisation issues. The names of actions will change from language to language - as will things such as keyboard mnemonics and keyboard shortcuts (what if a keyboard map is different). Secondly, flexibility. Users with different roles for example might get different config files which hide those actions it makes no sense to give them (e.g. hide admin options from non-admin users). It also lets you customise an interface to a users own requirements - you can allow them to change their keyboard shortcuts, position on menus etc., the result of which will be a user specific xml file stored in their profile. I'd admit you loose complie-time checking capabilities, but here I think its a justified tradeoff. Firstly, for internationalisation issues. The names of actions will change from language to language – as will things such as keyboard mnemonics and keyboard shortcuts (what if a keyboard map is different). Secondly, flexibility. Users with different roles for example might get different config files which hide those actions it makes no sense to give them (e.g. hide admin options from non-admin users). It also lets you customise an interface to a users own requirements – you can allow them to change their keyboard shortcuts, position on menus etc., the result of which will be a user specific XML file stored in their profile.
I’d admit you loose complie-time checking capabilities, but here I think its a justified tradeoff.

]]> By: Gabriel Mihalache http://www.magpiebrain.com/blog/2004/02/23/swing-action-configuration-goodness/#comment-207 Gabriel Mihalache Mon, 23 Feb 2004 12:34:19 +0000 http://www.magpiebrain.com/2004/02/23/swing-action-configuration-goodness/#comment-207 WHY would you want to use XML for this? No only do you loose strong typing, but you'll also have to work to keep the XML file synchronized with the Java classes. WHY would you want to use XML for this? No only do you loose strong typing, but you’ll also have to work to keep the XML file synchronized with the Java classes.

]]>