OK with me. On 6/28/13 1:58 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>Do you mind if I put out an official tweet about this? > >Om > >On Wed, Jun 26, 2013 at 6:51 AM, Alex Harui <aha...@adobe.com> wrote: > >> Sorry, forgot to mention that the FlexJSOverlay is updated on [1] >> and examples are at [2] with view source enabled for the Flash versions. >> >> [1] http://people.apache.org/~aharui/FlexJS/ >> [2] http://people.apache.org/~aharui/FlexJS/DataBindingTest/ >> >> On 6/26/13 3:50 AM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> >>wrote: >> >> >Very cool :) >> > >> >for your mail I thought that examples had this update but I can't see >> >modified examples in the commits? maybe I'm missing something? >> > >> > >> > >> >2013/6/26 Alex Harui <aha...@adobe.com> >> > >> >> Hi, >> >> >> >> I just checked in the beginnings of {} databinding in FlexJS. If you >> >>look >> >> at the source code, the SimpleBinding and ConstantBinding beads that >> >>were >> >> in the earlier examples are replaced by {} expressions. The compiler >> >> generates a data structure describing the bindings, and a bead >> >>interprets >> >> the data structure and sets up the bindings as needed. In this early >> >> version, the binding bead is looking for a specific pattern that can >> >> resolve to what should be faster ConstantBinding and SimpleBinding >> >> expressions. The rest of this week I'll be working on more and more >> >> general and complex cases. >> >> >> >> The reason binding is applied by a bead is because it allows you to >> >> optimize by replacing general databinding beads with beads that know >> >> something about the binding context. For example, in this prototype, >> >>the >> >> ViewBaseDataBinding bead knows that it is setting up bindings for a >> >> ViewBase which means that it can make assumptions that, for instance, >> >>the >> >> applicationModel structure itself will not be changing (its >>properties >> >> will, but not the reference to the model). And that means you can >>use >> >>one >> >> less watcher and you can apply initial values at initComplete and not >> >> necessarily at the instantiation of each widget. >> >> >> >> -Alex >> >> >> > >> > >> > >> >-- >> >Carlos Rovira >> >Director de Tecnología >> >M: +34 607 22 60 05 >> >F: +34 912 94 80 80 >> >http://www.codeoscopic.com >> >http://www.directwriter.es >> >http://www.avant2.es >> >>
