I think my initial instinct to put the bindings on the YAML side were right after all. But, this requires much larger changes.
I think I have the right approach though...I will define bindings as a totally stand-alone separate root node, after all the UI elements have been created. Unlike JavaFX, I will not put the binding definition directly into the property value (since that entails an ugly hack like "bind: binding expression"). This way we will have a very clear separation of concerns, just like with the "layout" component (i.e. not putting layout info at the control level, but in a separate node of its own).
Here's a sample of what it *may* look like on the YAML side:
(see the "binding" node at the end):
http://code.google.com/p/javabuilders/source/browse/trunk/org.javabuilders.swing/samples/org/javabuilders/swing/samples/binding/BindingFrame3.yaml
I did major updates to the core engine to support multiple root nodes, so major instabilities in the code right now (probably)...will continue on this.
Wednesday, April 30, 2008
Subscribe to:
Post Comments (Atom)
1 comments:
Runes of Magic is a Massively Multiplayer Online Role playing Game without monthly costs all kinds of Rom Gold and free to download. The premise is that you have played this game and understand the necessary Runes of Magic Gold in the Runes of Magic game. Perhaps the first monster I saw taken down in the demo can gain those varieties of Runes of Magic money. Characters choose one class; the important one is that we have to buy Rom Gold first. You can switch freely between the two classes, but you can only use primary abilities from your primary class, along with cheap Runes of Magic Gold, secondary abilities from your secondary class.
Post a Comment