It may sound obvious but I did it wrong for a while…
When you create a Cordova (Phonegap) application and you want to use npm modules don’t add them within the www folder, use the Cordova project root instead, otherwise the generated node_modules folder will get compiled and added to your build.
The final project structure (as of Cordova 4.0) should look something like this:
| \---package.json // npm project config file
| \---gulpfile.js // Gulp config file
| \---karma.conf.js // Karma test runner config file
The node_modules folder is safe here, it won’t be added to the app build.
The only thing that you have to bear in mind is that configuration files paths have to be prefixed with www.
When you are inspecting the DOM in Chrome Dev-tools there’s a yellowish tooltip that displays information about the currently hovered HTML node.
To get rid of it just press CMD (OSX) or CTRL (WIN) while hovering the Element’s panel in dev-tools.
Happy inspecting :)
I have a calendar grid where each grid cell has an ng-click handler that takes me to the day’s detail view.
At the same time, each grid cell can have an indeterminate amount of events associated, each with an ng-click handler associated that displays the selected event details on a popover.
As you can see there’s a conflict here. When you click on a calendar event there will be two ng-click handlers executed (because the event is bubbling), one will display the popover and the other one will go to the day’s detail view. Not what we want.
Thankfully ng-click scope exposes the $event property, which is the DOM event being propagated.
You can use the DOM event stopPropagation() method to stop event propagation.
Whe you modify a filename by just changing to upper/lowercase Git won’t detect it (at least on OSX).
When you want to perform such action you have to explicitly tell Git what’s changed.
Say we have the helloWorld.js file already commited but we want to actually call it HelloWorld.js.
The following Git command will do the trick:
$ git mv -f helloWorld.js HelloWorld.js
A few CSS tricks to emulate a native mobile application layout.
I hate the fact that inline-block elements don’t support spaces between them, it’s weird…