Hmm, that is a bit disappointing.
I hoped it would use the setters/getters where supported and only fall back
to the timers otherwise.
>From this perspective KnockoutJS is still my favorite :)
I suspect that with timers there may be all sorts of other issues when the
events will fire out of the e
It doesn't use a timer, it checks for changes when any angular event is
triggered. For example, if you do an ajax request, the response coming back
and being handled will trigger an $apply. If you're handing your own events
or doing some logic out side angular, you simply call scope.$apply
somewher
Like I said, I'm not entirely sure what triggers the polling (whether
it's a timer or an event). Doing it with many event handlers or
getters and setters has its own set of problems.
I did an object validation thing back in 2005 that was a really
simplistic version of this, and it actually worked
Just wondering if there were any guidelines on posts about events which are
not necessarily directly related to Ruby?
Iz
--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To view this discussion on the web visit
https://groups.google.c
Yes, because a controller action or watcher may modify a model
which may cause other watchers to fire, there may be multiple
digest cycles.
On Mon, Jul 2, 2012 at 4:29 PM, Simon Russell wrote:
> It's definitely a polling design, from what I can see:
> https://github.com/angular/angular.js/blob/m
It depends how many objects you have in your
controller scopes. As the digest time is linearly proportional to this,
Hundreds is not noticeable, thousands are a bit iffy.
In general there needs to be better support for streaming and manipulating
very large collections in angular, maybe one of us co
Ivan is right. It just uses plain old object comparison.
However it's not timer based, basically it recomputes changes every
time there is a user action (like a click) and also after each controller
action fires they call this the digest cycle.
If you have some code that updates models behind angu
There are trade-offs to all methods, with plain old object comparison,
you pay the price right up front, i.e. a small performance hit. But
the benefit is that the semantics are crystal clear.
With event subscription, you pay a different price many times over.
You introduce subtle semantic problems
Nothing specific in the way of guidelines - but if it's not development
focused, then I'd be wary. If you've got something you want to post and you're
not sure whether it should be here, you're welcome to contact me off-list to
discuss further.
Cheers
--
Pat
On 02/07/2012, at 1:31 AM, Iz103
Thanks Glen,
It makes more sense now.
I will definitely give AngularJS a go in my next project.
Cheers.
On 02/07/2012, at 17:45, Glen Maddern wrote:
> It doesn't use a timer, it checks for changes when any angular event is
> triggered. For example, if you do an ajax request, the response com
NEW MEETUP
Mutant Mudules
The Brisbane Ruby and Rails Brigade
Added by Nigel
Monday, July 23, 2012
6:00 PM
Toowong Library (Meeting Room)
9 Sherwood Rd
Toowong Village Shopping Centre
Toowong
Mutant Modules
- Ruby Modules - Nick
- JetBrains new YouTrack Agile Project Management - Pau
Hi everyone,
Rorosyd is on again in a week: Tuesday July 10, 6:30 for a 7pm start.
At our usual: Trinity Bar in Surry Hills: http://tinyurl.com/6emfna
This time there will be no impostors. (I am looking at you Sydney Hipsters
Service Design something something)
A big welcome back to Sydney to
Hi,
I wonder if the FreeTDS link is actually broken or there's something wrong
on my side?
brew install freetds
==> Downloading
http://ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-0.91.tar.gz
curl: (22) The requested URL returned error: 404
Error: Download failed:
http://ibiblio.org/pub/Li
13 matches
Mail list logo
