More AngularJS Magic to Supercharge your Webapp

Make way for another amazing article which covers more of AngularJS Due to the popularity of the previous article, Use AngularJS to power your web application, I've decided to cover more of AngularJS to make it fun and easy for all developers to play around with it. AngularJS is an incredible tool, but a lot of the more advanced features are hidden in deep within the documentation and others are too tricky to learn direclty. AngularJS is also a fairly new product and as a result there are many features that are yet to be discovered and blogged about. This article will cover more of the hidden gems of AngularJS and introduce new development tricks and methods to supercharge your AngularJS application. Pleaes read onwards if you wish to become an AngularJS web guru :). This page was first published on October 2nd 2012 and was last updated on January 30th 2013. This article is a sequel to the previous article titled Use AngularJS to Power Your Web Application. OK so onto business. Oh!

Use AngularJS to Power Your Web Application AngularJS is a truly amazing approach to developing JS-heavy web applications AngularJS, by Google, is a well-organized, well-tested, versatile, powerful and flexible JavaScript MVC framework for building rich client-side applications. You still may need to have a server-side backend, but the majority of the user-interactivity logic will be delegated to the client-side. This page was first published on August 15th 2012 and was last updated on October 29th 2012. This article briefly outlines what Angular can be used for and the basics of how it works. This article also explains how angular can be used with MooTools and JQuery in harmony. When you decide to build a website using angular the major question to ask yourself is that is this a website that requires valid HTML or is this a web application that focusses more on functionality then markup. Just like any MVC architecture, URL paths are routed to controllers and the parameters are available within the controller method.

Logging Client-Side Errors With AngularJS And Stacktrace.js Last year, at cf.Objective(), I was watching Elliott Sprehn give a presentation on Production Ready JavaScript. In part of the presentation, he was talked about client-side errors and recommended that everyone log client-side errors to the server. To be honest, before he mentioned it, I don't think that it had ever occurred to me! Before that, I had only ever logged server-side errors. View this demo in my JavaScript-Demos project on GitHub. AngularJS has excellent error handling! To help me and my team iron our JavaScript errors, we needed to intercept the core AngularJS error handling and add a server-side communication aspect to it. Posting the error to the server was only half the battle; it turns out that getting the right error information out of a JavaScript exception object is not super easy, especially across multiple browsers. In the following code, I've tried to isolate all of the error handling aspects of my AngularJS application.

How to make your AngularJS app work in IE 8 | HYPOPORT IT Blog Written by Andreas Marek (@andimarek). We (the team I work in) are developing an AngularJS application for the last several months. Most of our customers are still using IE 8, so we need to support that browser. Our app is using AngularJS 1.1.5 and jQuery 1.x. A few weeks ago it was time to make our app work in IE 8. We had to deal with three main problems and some “normal” IE problems regarding html and css. Problem 1: Ajax caching All browsers don’t cache Ajax requests, except IE. We decided to set the http response header ‘cache-control’:’no-cache’ for every http Ajax response. You don’t need ‘pragma’:’no-cache’ or any other additionally headers as sometimes suggested. Problem 2: Custom html elements (Important: Because our app has jQuery 1.x included Angular uses jQuery instead of jqLite. This was our biggest problem we had to overcome. Our app uses ng-view and around 10 custom elements. Solution: Extending jQuery’s internal list of html elements to Problem 3: ng-repeat and html5 elements