FXML expression binding

Werner Lehmann lehmann at media-interactive.de
Tue May 7 02:42:28 PDT 2013

See below.

On 07.05.2013 01:56, Richard Bair wrote:
>> ! boxD.selected&&  boxE.selected seems to be: !(boxD.selected&&  boxE.selected)
> I'd probably call that one a bug. Whether it was or not!

I would agree. Looks to me as if there might be special code checking 
for a '!' at the beginning of the expression. Regardless whatever comes 

> At the time, I really wanted us to use UEL (same expression language used by JSF, JSP) for the following reasons:
>      - EE engineers will be familiar with it
>      - Lots of example code out there
>      - Implementation already exists and is robust
> There were a few things I felt needed fixing in UEL to be quite what
> I wanted, but basically I felt we should take it and go. Since then
> some other binding languages have come on the scene such as
> handlebars and I don't remember how many others we looked at. Should
> we just take UEL, or should we take a full survey of the JS
> state-of-the-art?

Personally I don't know UEL (used only OGNL on Tapestry). Not sure if 
UEL documentation 100% applies to FX beans/properties when it is 
intended for EE beans. For example, what about obserable properties, or 
the #{} syntax. If that is clarified I'd be happy with the choice.

The "Parameterized Method Calls" feature might even help to resolve 
RT-19198 which is about preselection in selection models in FXML. One 
problem here: select() is a void method, so there is no good result of 
that expression and in this case you wouldn't want to use it anyway.



More information about the openjfx-dev mailing list