How Bindings and Observables work

A quick walkthrough

Bindings are good because you don’t have to worry about propagation, you just declare data binding on your view components, and the value will just be there on both sides: the UI component and in the model.

DSWeb 0.0.12 and ds-bean 0.4.10

An important, possibly compile breaking change with ds-bean 0.4.10 is that the BindingRegistration interface returned by bind methods is now changed to the existing ListenerRegistration. This is useful if you have to keep track of added listeners and bindings. The meaning…

DatePicker name and format changed

(0.0.11-SNAPSHOT)

The most important thing is that “Datepicker” is now renamed to “DatePicker” as it’s usually easier to find it that way.

Changing SelectModel, better supporting null options

Select was extended by adding withNullOptionCaption and bindNullOptionCaption methods, and thus its model was extended. To support this, SelectModel was renamed to AbstractSelectModel (because TypeaheadModel extends it), and only the new…

Selected stories

Automatically propagating two-way bindings work like a charm. Until things get a bit complicated. It’s pretty okay if an input component is bound to a value. If the user enters a value, it will just be there in the model. If you update the model, the user will just see it. Fine.