“Superheroic” is how the AngularJS team at Google describe their framework – not an inaccurate description judging by its legions of fans and developers.
By eliminating a lot of the complexity usually involved with building single-page web applications, AngularJS has become one of the most widely used development frameworks around. In fact, it’s fast becoming the de facto method for rendering dynamic content on a static webpage.
So what about those of us who haven’t joined the bandwagon? What’s involved in switching an existing web application to the AngularJS framework?
A few customers have asked us whether we plan to ‘support’ AngularJS in the future, or how a KeyLines application would fit into a wider AngularJS application, so we built a KeyLines Angular Directive.
Here’s a copy of his slides. We hope they provide a useful starting point if you’re thinking of switching to AngularJS.
Postscript: KeyLines and AngularJS
Despite our initial frustration, we don’t actually hate Angular. We’ve overcome a lot of the initial hurdles to build a functioning KeyLines directive in the framework.
If you would like to speak about integrating a KeyLines component into your Angular application, just get in touch and we’ll gladly talk you through the options.