I asked Glen the same question on the night after his talk. I can confirm
the internal timer and some "magic" around the object comparison.

Samuel Richardson
www.richardson.co.nz | 0405 472 748


On Mon, Jul 2, 2012 at 4:12 PM, Ivan Vanderbyl <[email protected]>wrote:

> Hi Dmytrii,
>
> In a nutshell from what I have read it uses an internal timer which
> continually checks the value of all keys against the last known value. I'm
> not sure how efficient this is but it seems to be pretty fast in the
> smaller apps where I've seen it used.
>
> — Ivan
>
> On 02/07/2012, at 4:08 PM, Dmytrii Nagirniak wrote:
>
> Hi,
>
> The angularjs looks really great. I have been a big fan of KnockoutJS
> which is similar to angularjs in some aspects.
>
> But I wonder how angular can do the two-way binding on plain JavaScript
> objects?
> JS doesn't _generally_ have setters and getters and it gets even more
> complicated with arrays.
>
> KnockoutJS solved those problems by wrapping every property/obect in
> "ko.observable/ko.observableArray".
>
> I don't understand how angular does that. It must be doing some
> "smart-ass" things during the compilation.
>
> Anybody knows that?
>
> Cheers,
> Dmytrii
>
> On 29 June 2012 11:41, Ben Hoskings <[email protected]> wrote:
>
>> For those that didn't see Glen's talk, have a quick look at the slides.
>>
>> In particular, check out the embedded HTML examples. They're hooked up to
>> their corresponding iframes using angular.
>>
>> Try editing the {{ handlebar-like }} snippets to see how angular glues it
>> all together. It takes almost no JS to make that happen.
>>
>> - Ben
>>
>>
>>
>> On 29/06/2012, at 11:34 AM, Glen Maddern wrote:
>>
>> > Here's my talk on AngularJS from last night:
>> >
>> > http://sup-angularjs.herokuapp.com/
>> >
>> > If that's whet your appetite for writing awesome frontends with hardly
>> any code, go have a look at the source:
>> >
>> > https://github.com/geelen/angular_presentation
>> >
>> > AngularJS is pro, don't you want to be pro?
>> >
>> > -glen
>> > @glenmaddern
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Ruby or Rails Oceania" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to
>> [email protected].
>> > For more options, visit this group at
>> http://groups.google.com/group/rails-oceania?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby or Rails Oceania" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/rails-oceania?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/rails-oceania?hl=en.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/rails-oceania?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to