Thanks for the detailed explanation Martin - it does make sense. This is a tricky one as I can understand the rationale but it does feel like it leaves a limitation to the binding layer. Manually adding a custom converter can be done but it feels like a workaround - perhaps this could be added (generic coercion against the widget value type) inside of the form controller so that the end developer does not need to be aware. -- View this message in context: http://qooxdoo.678.n2.nabble.com/data-types-for-form-fields-and-their-affect-in-data-binding-tp5286833p5292182.html Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
