I’ve just finished working on a very large project written in React and Redux. The whole team were new to both and we loved them.
I’m going to share my experiences of experimenting in Angular 2 with you, from the point of view of someone who needs a pretty compelling reason to move away from my JSX and reducers.
The Journey So Far Let me highlight a few key moments in my UI development experiences, to give a bit of context to my ramblings.
In the past I’ve used RequireJS with AngularJS. It’s an awful mistake. It leads to a big jump in complexity with no benefts. Angular apps don’t work well with AMDs, so really your are using RequireJS to combine files into one big file.
Understanding Memory Leaks What is a Memory Leak? Why is a Memory Leak Bad?
If you need modals in an AngularJS application, look no further. I’ll show you how to use the Angular Modal Service to add Bootstrap Modals or your own custom modals to your application.
See it in a fiddle or check out a full set of samples online.
Contents [Using the Angular Modal Service](#UsingTheAngular ModalService) A Quick Example Design Goals How It Works Wrapping Up Using the Angular Modal Service Here’s how you can use the Angular Modal Service to add a bootstrap modal to your application.
Promises are a core feature of AngularJS - whether you understand them or not, if you use AngularJS you’ve almost certainly been using them for a while.
In this post I’m going to explain what promises are, how they work, where they’re used and finally how to use them effectively.
Once we’ve got the core understanding of promises, we’ll look at some more advanced functionality - chaining and resolving promises when routing.
I’m going to be working in F# almost exclusively for a short while, so before I throw myself into that I wanted to wind up my Practical AngularJS Part 2 article. It’s ready to rock here:
Practical AngularJS Part 2 - Components of an AngularJS Application
In this article we get a brief introduction to what’s in the toolkit for an angular developers - filters, controllers, services, directives, views and routes.
There are some interesting things in the article for angular too - a look at using directives for custom elements, how to handle both the DOM and Angular loading correctly, and timers and intervals.
I was recently at Devoxx in Antwerp, primarily because I wanted to get involved in some of the sessions that were being hosted by guys from the AngularJS team at Google. I’ve had a chance to work a little with Backbone and KnockoutJS and had been recently deliberately holding off looking at AngularJS so I could hit the conference and workshops fresh and unencumbered with any preconceptions.
The sessions were great, and since then I’ve been working on a couple of projects that use Angular.