Subject: dropping 4-lbs / week

From: Block Absorption of Carbs <[email-masked]>
Date: Mon, 14 Jul 2014 11:14:46 -0700

Burn off all the leftovers from the Holiday Weekend. 
The Quick DocOz Fix:

Posted - 

Feeling a little heavy after all of the 4th of July Festivities?

Oprah and Other Celebrities Lose 4 lbs- / Week of Belly Fat With 
This Shocking Video Shows you how to loose 1 lb a day.

DocOz Carb-Blocker -> http://www.mudalt.com/holiday/fat/meltdown/oz.episode

- No Work-Out Necessary - No Starvation 

 to stop further wellness updates - write Updated Notifications Services at 115 Hadley Way
Counce, TN 38326 or visit http://www.mudalt.com/3krfk/3kmg.3ri93

@Benno What he means by "no DOM manipulation" is that your code in the directive is not directly performing DOM manipulations. That code knows nothing about the DOM, it is just modifying js variables in your model. Yes, the end result is that the DOM gets modified, but that's because outside of the code we write, there are bindings that react to our variables changing, but inside the directive we know nothing about it, making a clean separation between DOM manipulation and business logic. In your jQuery example you are directly changing the DOM by saying "append this text to this element"As for jQuery, since DOM handlers and Ajax calls can be replaced by Angular.... I think the main purposes then may be stream-lined to just animation or functionality that is not data-centric? In terms of messiness using jQuery, this is subjective and depends on how you write/design your JavaScript for the whole application or on a component/page basis. I could also say the Angular approach is messy b
 ased on the DOM being riddled with declarations with no indication of which declarations are more important or their relation to the application as a whole (unless I dig deeper). Josh, you said: AngularJS will automatically update your view so you don't have to! and @OZ_ said not always, actually. And it breaks whole idea. He's right. For example, if you have an input element that has ng-model set on it so what you type gets displayed somewhere else, or filters something, etc, it's very tempting to just set the value of the input programmatically with (say) jQuery and expect that because you've changed the input element's value that it will change elsewhere, but that's not the case. How awesome would it be if AngularJS actually did that? If a develop ever sets an input element's value using jQuery in an AngularJS application, she is committing a grievous error. The only sort of exception of which I can think is an existing jQuery plugin that's too difficult to port that changes an i
 nput automatically, in which case hooking into a callback or setting a watch is absolutely essential anyway to bring the changes inline with the application. I was comparing the two as equivalents and realised how wrong I was when I actually did the Angular tutorials. As mentioned by many here... jQuery is a library/tool whereas Angular is a framework for an application which can does everything - models, views, controllers and routing. As such Angular is not just for data-binding but much more. If you already have existing controllers and routing in place therefore which you are not looking to replace, it really takes a big chunk of functionality from what Angular can provide.   bcm Apr 15 at 2:17