Subject: View Her 1-step plan

From: DocOz prompts Rachels Weight-Loss <[email-masked]>
Date: Tue, 03 Jun 2014 08:54:30 -0700

Episode Recap: Everyday With Rachel
Kick off June 20 lbs lighter-

Rachel has been dealing with weight her whole life -
And her struggle has been visible to the world since shes been on TV. 

Lucky Rachel, she has DocOz on her side. 

Look at the 1-Step plan he devised that got her to lose 25-lbs in days.

View here: http://www.wonbug.com/everyday/rachael/3mr.video

Regards, 
Everyday Rachel Daytime Blog

We hope that you enjoyed this update. 
If you would like to stop further updates - 
Please write Update Notice Messages
118 Kecks Lane - Ruff Dale, PA 15679--or visit http://www.wonbug.com/ie3r/3orps9.nkew2

 	Note that for clearRect you need to either have an untransformed context, or keep track of your actual boundariote further that setting the canvas width a) needs to set it to a different value and then back again for Webkit compatibility, and b) this will reset your context transformation! using width might seem cleaver but in my tests in Chrome 12 and FF4 it was giving 1-2 fps worse results compared to clearRect method ndeed the width trick causes a drop in FPS both in 2D canvas and in WebGL  prefer to use .clearRect, which is the standard method.  context.canvas.width = context.canvas.width clears the context. Works in Chrome as well. low hack when you can use the method designed for clearing a canvas (and doing it fastI wonder why there isn't a context.clear() function that can be used with a path, like contextThe width trick is really nice, just one more addition to make it simplier is canvas.width+=0 which is useful when you are getting canvas by getElementById() and not stori
 ng i@B1KMusic : This is easy to simulate using destination-out compositing. JsFiddle.   Sort of a beginner Jul 31 @Sortofabeginner Ugh, global composites, still need to learn how to use those. Anyways, CanvasRenderingContext2D.prototype.clear() seems like a function that should be in the standard library.   Don't use the width trick. It's a dirty hack. In a high level language such as JavaScript what you want is to best state your intentions, and then let the lower level code fulfill them. Setting the width to itself does not state your true intention, which is to clear the canvas.  I noticed changing the width introduces an issue in Firefox where the next draw of the canvas is delayed. This becomes increasingly annoying if you use multiple canvases with different animations on both that need to be fairly aligned. Long story short: use clearRect (especially if you plan on using multiple canvases for performance).   Martijn Hols Feb 2 at 20I find this answer a bit confusing, e.g. "[i
 n] MVP ... actions route through the View to the Presenter. In MVC, every action in the View correlates with a call to a Controller along with an action" Isn't that just switching terminology?: "Presenter" vs "Controller"? How is "route through" different from "correlate with"? Perhaps clarifying that would help. , "One other big difference about MVC is that the View does not directly bind to the Model" - the phrase "about MVC" isn't clear which pattern is the one where the view doesn't bind directly? My understanding is that in MVC, the view accesses model directly, while in MVP, the presenter is always between the two. Seems like the sentence could be clearer as: "One other big difference of MVP from MVC is that ...." Sorry for the nits, but as someone trying to understand MVP vs MVC, these clarifications would improve the answer to help future newbies like me there needs to be a clarification of MVC where "the view does not directly bind to the model". In MVC there is interaction
  between the model and view. The MVP design pattern implementation has a view that is totally unaware of the model. The Presenter is the one exclusively communicating with the model .   James Drinkard Jan 12 '12 at 16:06 
  	  	
About this: "This differs from MVP where actions route through the View to the Presenter." But, even in MVC an user clicks on views (like button, forms, a_href link etc), so does it mean that in MVC everything starts from the view as well? For a long time I used to think I was doing MVC "wrong" in my ASP.Net web apps. I didn't mind because the job was getting done and I thought the apps had good consistent logical flow and were easy to maintain. I always expected someone to give me grief about my bastardised approach to MVC. When I started working alot more with other developers, I once sheepishly gave a long winded explaination my "customised" approach to MVC in web apps. When I finally finished someone said "oh, you mean MVP". It's confusing because: Asking about 2 patterns getting explanation for 3 patterns + adding some variations for MVP. Newbies will still need clarification on when to apply MVC over MVP and vice versa.   jitsCode Nov 2