No need to use the Uize.Widget.mBindings mixin in the mV2 mixin, since we can just aggregate the bindings mixins individually, and this reduces the code size.
Implemented support in the htmlt compiler for the ? (show) binding type.
Fixing Pos's getCoords translate* detection
More getCoords() translation detection stability
Implemented support for value bindings to checkbox tags.
Some minor code size optimization of the button widget.
Optimized the button widget class by switching to using derived properties where possible.
The addChildren gets promoted to being a method of the Uize.Widget base class. This method shouldl be used in place of the addChildButton method in the Uize.Widget.Button class, as well as in other places where it is convenient.
The Uize.Widget.Button class gets a simple action state property for convenience in simple cases where you just want to instantiate a button widget that has a click action.
Pass the DOM event as an argument to the action function
Updated some widgets to use the addChildren method in place of the ugly old addChildButton technique.
Yeah, followLink, my ass!
Eliminated the static handling for the addChildButton method in the new Uize.Widgets.Button.Widget class. Eventually, all usages of this old technique will be eliminated and the method will be eliminated entirely.
Eliminated some more usages of the old addChildButton method of the button widget class.
I can't see a compelling reason, in this day and age, to have this "soft" adding behavior - where was this ever needed?
Eliminated one more use of addChildButton.
EEliminated one more use of addChildButton.
Fixed a bug with the logic for determining the module name for generated namespace modules for folders.
Minor tweaks.
In order to further reduce the code size of the V2 widget base class, I removed the default html generation code that is useful for plain container widgets and created a dedicated Uize.Widgets.Container.Widget class. This actually makes the various examples and module code that wants to use this behavior of children HTML generation semantically cleaner and easier to understand, anyway.