flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Left Right <olegsivo...@gmail.com>
Subject Re: [jira] [Updated] (FLEX-51) Please check support for ExactValue initializer
Date Tue, 24 Apr 2012 18:28:46 GMT
> I consider the current binding system to be consistent.
No, it's not. It is possible to get the same code compiled with all the
same settings and get different behaviors. This is exactly what consistency
is not.

What I would be looking for is that the non-binding attributes were the
defaults, that MXML promised a deterministic order of binding, and that the
present model be fixed to actually do what it
looks-like-it-does-but-not-really. I.e. employ the mechanism that ensures
that all bindings were assigned values provided in attributes, and that the
later be made clearly distinct and alert users on potential overhead.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message