| ==================================================================== | |
| Simple-as-possible instructions to add a field (or more) using South | |
| to an existing Django model with existing data. | |
| ==================================================================== | |
| Two versions: | |
| 1. Super-condensed (the bare minimum - jfdi) | |
| 2. Detailed-but-brief (if you want more information). | |
| Notes: |
| <!DOCTYPE html> | |
| <html> | |
| <!-- NOTES | |
| Demo - uses IOS native scroll available in IOS5, but sidestep the document-bounce behavior. Tested on iPad 1, using IOS 5.1. | |
| This approach uses a set of 3 nested divs. | |
| OuterDiv -- fixed height, width, overflow-scrolling: touch; | |
| MiddleDiv -- fixed height width, overflow-scrolling: touch; fits inside OuterDiv | |
| InnerDiv -- fixed height width, bigger than MiddleDiv, so it kicks in the overflow behavior |
| /* ---------------------------------------------------------- */ | |
| /* */ | |
| /* A media query that captures: */ | |
| /* */ | |
| /* - Retina iOS devices */ | |
| /* - Retina Macs running Safari */ | |
| /* - High DPI Windows PCs running IE 8 and above */ | |
| /* - Low DPI Windows PCs running IE, zoomed in */ | |
| /* - Low DPI Windows PCs and Macs running Firefox, zoomed in */ | |
| /* - Android hdpi devices and above */ |
| /** | |
| Returns a bounding rect for _el_ with absolute coordinates corrected for | |
| scroll positions. | |
| The native `getBoundingClientRect()` returns coordinates for an element's | |
| visual position relative to the top left of the viewport, so if the element | |
| is part of a scrollable region that has been scrolled, its coordinates will | |
| be different than if the region hadn't been scrolled. | |
| This method corrects for scroll offsets all the way up the node tree, so the |
When using directives, you often need to pass parameters to the directive. This can be done in several ways. The first 3 can be used whether scope is true or false. This is still a WIP, so validate for yourself.
Raw Attribute Strings
<div my-directive="some string" another-param="another string"></div>
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
