A bunch of links to blog posts, articles, videos, etc for learning AngularJS. This list is in its early stages. Feel free to submit a pull request if you have some links/resources to add. Also, I try to verify that the articles below have some real content (i.e. aren't 2 paragraph blog posts with little information) to ensure I'm not listing "fluff" pieces. If you have an idea for a better way to organize these links, please let me know. As I find similar posts in the "General Topics" section, I will break them out into their own categories.
One build tool that I really like isgulp. If you're not familiar with gulp, the cool thing about it is that it uses node's streams as a performant piping mechanism to connect multiple tiny modules that do one thing, and one thing well.
Now back to Angular and the tedious process I explained before. Withng-annotatethe inline array annotation becomes unnecessary, even though your code can still be minified.
Spotify is a great way to stream all of your loved music. As nearly all great services have a public API today, so has Spotify. In this tutorial I will show you how to login to Spotify, access your playlists, read the track data and also play some music snippets. Everything will be wrapped inside a mobile app using the great Ionic Framework.
In this tutorial, we will use AngularJS to build this simple Todo Chrome Extension:
Since the release of the iOS 8 SDK, developers have access to the HealthKit App and its services. Through this service you can read and write body data like weight, height or store a complete sports workout session. To implement this feature in your Ionic app, you can make use of thengCordova wrapper for cordova plugins, and that’s what I will show you today.
We will make a simple App to write some general data and to submit a complete workout to the Health app, which will then be displayed inside the standard iOS app.
Since e2e tests are much more expensive than unit tests - e.g., they generally take more time to run and are harder to write and maintain - you should almost always focus the majority of your testing efforts on unit tests. It’s good to follow the 80/20 rule - 80% of your tests are unit tests, while 20% are e2e tests. That said, this tutorial series breaks this rule since the goal is to educate. Keep this in mind as you write your own tests against your own application.
The Angular team faces a problem. How do you talk the great new features of Angular 2.0 under development without damaging use of the current 1.x? This effect is often called the Obsborne effect, named after a 1980s computer company whose marketing contributed to putting the company out of business. In short, the better 2.0 sounds, the less people will want to start or continue projects built with 1.x.
We mostly use AngularJS as our JS framework of choice. We don’t want to enter the current flame war; we simply think it is great. We don’t buy the “it’s too complex” argument - we do software development so we have to understand the tools we use. The AngularJS abstraction and terminology are what they are, but once you wrap your head around that, they make a lot of sense. The depth of the framework is why it is called a framework, it solves a lot of common pain points in an elegant and efficient way. Mostly…
The only argument that we do agree with is that it can be fairly common to get UI performance issues in AngularJS. DOM manipulation is far from being optimal, and watchers trigger DOM rebuilds fairly often. To be fair we have upgraded from Angular 1.2 to 1.3 and it is getting better, but not good enough to get the native touch we are looking for on the most complex pieces.
Promises are a great solution to address complexities of asynchronous requests and responses. AngularJS provides Promises using services such as $q and $http; other services also use promises, but I will not discuss those here.
Promises allow developers to easily attach 1x-only notifications of response to any asynchronous request/action. Promises also enable two (2) other very important things. We can:
Transform the responses before subsequent handlers (in the chain) are notified of the response.
Use the response to invoke more async requests (which could generate more promises).
But even more important than the features above, Promises support easy chaining of custom activity or computations. Managing sequences or chains of asynchronous activity can be a very difficult and complex effort. Promise chains are amazing and provide means to easily build sequences of asynchronous requests or asynchronous activity.
If you're reading this, you most probably tried to make a long and/or complex list of items using a ng-repeat directive, and after seeing how it performs in terms of speed, felt like AngularJS failed you.
State management within Angular started out as a single celled organism if you will in the form of a single controller managing all the state for the application. If this is a single page application, one controller makes sense right? We emerged out of the ice age by starting to group our views and controllers into smaller, self-contained units either within a directive or a route. This was a vast improvement, but there was still the problem of managing complex state within our applications. It was not uncommon for us to have bits and pieces of state strewn across our application tucked inside of controllers, services, routes, directives, and occasionally, in our templates. Mutable state in itself is not inherently evil but shared mutable state is a recipe for disaster.
Angular 2it is just around the corner and people are still afraid becauseAngular 2changes too much and it will hard to migrate. That is not true at all, in fact you will see how easy isAngular 2by highlighting the semantic shift between those two.
Let’s migrate a directive from Angular 1 to Angular 2. I love accordions, everybody love accordions! Let’s migrateui-bootstrapaccordion toAngular 2. I can’t assume that you’re familiar with it, so we are code both at the same time, explaining the differences along the way. I highly recommend you to, at least, replicate yourself theAngular 2one.
Originally we were only thinking about getting feedback from the small group of developers that are already spending most of their day working on Angular 2. This quickly changed, however, as more and more people started submitting responses. Angular 2 is only in alpha and you cannot build production apps with it yet. It is probably safe to assume that many people who responded are just starting to learn about Angular 2. Therefore, we now view the results in terms of what developers think they will do in the future rather than what they are actually doing right now.
With that disclaimer out of the way, let’s get to the results…
In this three-part tutorial series we’ll be building an Etsy clone with Angular and Stamplay. Stamplay is a great development service that handles much of the server and API based stuff for developers. This means you as a developer can focus on the things that matter most to your users; things like user interface, interactions, […]
Implementing a login and user authentication system for your AngularJS app seems to be one of the hardest problems people encounter. My article on a simple login with Ionic and AngularJS is the far most viewed article on this blog, every day! As the mentioned article only describes a basic system for a very low level security, this article will highlight everything you need for a complete user authentication and login inside your AngularJS app!
In particular this means, this article will show you how to:
Log in a user and store the user session (Token based auth!)
Protect your routes based on authentication status and role of the user
Notice when an unauthorised request was made and a new login is required
Often developers will publish source code to a custom application or library on GitHub. Experienced developers will also document their code/solution with a detailed README, and perhaps Wiki pages. But those same developers often do not have convenient answers to the following issues:
How do you upload images that you want to be shown in the README file(s)?
How do you deploy alivedemo of your application or library?
The following two sections will show you how to accomplish these easily!
In some cases you might be able to avoid this problem by using paging or infinite scrolling, but sometimes that's just not good enough. For example, lists that are displaying only a few items at a time (like any kind of a log) would simply be very impractical from the users point of view. Another reason - you might be using libraries like SlyJS that load a whole list at once to calculate the size of the embedded scrollbar and to make list swiping and elastic bounds work properly. Ooooor - your client simply demands it. :)
Single page apps make a lot of sense for customer-centric applications that handle a lot of user data. SPAs are often tied to a RESTful API for a good reason: when your data makes sense, your experience makes sense. We just rebuilt our console – an Angularjs-based Single Page App – and spent a lot of time modeling out the REST API (the actual data model/structures).
With the user model mapped out, it’s much easier to build a UI for your API because the common things like list views, search boxes, sorting, etc – they just fall in place alongside your data model. Fronting a REST API with a single page app gives the assurance of sane data and the freedom to make your UI look and feel sexy. #winning
I've been an Angular guy for the past couple years, and I've gotten pretty good at it. I've seen its nooks and crannies, and I've grown fond of it.
But, like I said, it was hard to ignore React.
It's fast, it's light, it's new and shiny. So I dug in. I recently released an app, Farely, which I'd written in Angular. (Note: I didn't use directives like I should have.) I thought it'd be the perfect opportunity to try out React, since the app could be composed of components. It also wouldn't need anything React doesn't offer, like routing or complex data modeling.
And so I began the project. Below are my thoughts and observations, should they help inform your library choices. I'll assume you've been introduced to React and Angular, since there are great articles written about them elsewhere.
Understanding Memory Leaks What is a Memory Leak? Why is a Memory Leak Bad?Identifying Memory Leaks Method 1: The Wrong Way Method 2: The Timeline Method 3: Recording Heap Allocations Method 4: Heap SnapshotsAnalysing Memory Leaks Analysing the leak in Scenario 2 More on GraphsFixing Memory Leaks Three golden rules Anti-patterns to avoidThe Future Weak Maps AngularJS 2 Even Better BrowsersAppendices Thanks Mysteries Futher Reading
In this series, we'll be using AngularJS and Firebase to create a simple web application from scratch. It will be a simple blogging application where the user can sign in or sign up and publish a blog post.
This tutorial assumes you have basic knowledge of AngularJS, but it shouldn't be tough to pick up the topics along the way.
React JS Injection into Angular JS Application or Fighting for Performance Increase; Author: EastBancTech; Updated: 15 Aug 2014; Section: Client side scripting; Chapter: Web Development; Updated: 15 Aug 2014
Sharing your scoops to your social media accounts is a must to distribute your curated content. Not only will it drive traffic and leads through your content, but it will help show your expertise with your followers.
How to integrate my topics' content to my website?
Integrating your curated content to your website or blog will allow you to increase your website visitors’ engagement, boost SEO and acquire new visitors. By redirecting your social media traffic to your website, Scoop.it will also help you generate more qualified traffic and leads from your curation work.
Distributing your curated content through a newsletter is a great way to nurture and engage your email subscribers will developing your traffic and visibility.
Creating engaging newsletters with your curated content is really easy.