On 1/25/13 10:57 AM, "Nick Tsitlakidis" <ni...@perfectedz.com> wrote:
> Hello Alex,
> To be honest, your approach sounds like the proper way to move forward (at
> least to me), but I still think that using what we already have in the AS
> side is going to take less time and as you have already said in some
> emails, this year will be a crucial one for Flex.
>
> Anyway, having choices is always good. Time will show which one will be
> adopted by the community.
>
I'm not sure which one will take less time. I'm taking my approach because
I can set a low bar (the first one being using a simple form to get JSON
data, and view it in a list) and build up from there without setting
expectations that it is the same Flex SDK you know. The other approach will
probably be "incomplete" for a long time and have performance and fidelity
issues dealing with the APIs that relied on Dictionary and weak references
and other impedance mismatches between AS and JS.
Over time, the approach I'm taking can grow to match a significant portion
of the existing Flex SDK, but I would not want to promise 100% for the above
stated reasons.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
