Three Shades of Angular
After years of building business apps with Angular, I find it helps facilitate some incredible scenarios. Read on to learn more.
Join the DZone community and get the full member experience.Join For Free
In 2014, I presented at the Atlanta Code Camp and walked through building an AngularJS app starting from file —> new. I used test-driven development to demonstrate how to create a functional application. I also wanted to demonstrate an app with multiple controllers that communicate with each other yet don’t rely on $scope, $watch, or even event broadcasting.
You can view the source for the Angular health app, along with instructions to step through the build iterations, in this GitHub repository.
After years of building business apps with Angular, I find it helps facilitate some incredible scenarios, like this total rewrite of a Silverlight audit tool I did for a local physicians’ group:
To see an example of that in action, check out the Angular ES6 Health App. This is the same application, rewritten using the new features built into ES6. It is compiled to ES5 using Babel. I also used the combination of browserify and babelify to transpile the project into a single file for performance (as opposed to dynamically loading the modules). Don’t worry, I have an example of dynamic loading in the third Angular example.
If you want to see what the same app looks like using TypeScript and the next version of Angular (that as of this blog post is in beta), take a look at the Angular 2.0 Health App. This is the same app migrated to use Angular 2.0 beta, TypeScript, and AMD for dynamic module loading.
The migration wasn’t straightforward, so I wrote about it along with my thoughts on Angular 2.0 in the post Angular 2.0: Opinions, Commentary, and a Migration Case Study.
Published at DZone with permission of Jeremy Likness, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.