A few months ago Jake Archibald wrote an article about the awesomeness of the asyncfunctions in ES7 and how we can “emulate” them using ES6’s generators, using his spawn function, which has subset of the features of co.
In this blog post we’ll take a look at standard ways of handling asynchronous calls and how we can improve the readability of our code using generators. We’ll also take a further look at the implementation of spawn, since there are few tricky moments there.
React JS and Flux go together pretty well, as it was architected that way, but they’re by no means dependent upon one another. As a result, I’m going to split this article up into the React JS piece, which will go over how to create views and best practices, followed by a detailed look into how I’m getting data out of my mocked server API via Flux.
I’ve put a demo of the todo application in action, but prepare to be disappointed, as it’s really very straightforward.
In this post, I would like to explain Part 1 - How to setup AngularJS in MVC4 application. This is our First Post about AngularJS. Here I have explained a little about AngularJS and What we will learn in this section part by part. In this part (Part 1) I am going to explain how to setup AngularJS in MVC4 application.
The Flux architecture allows you to think your application as an unidirectional flow of data, this module aims to facilitate the use of RxJS Observable as basis for defining the relations between the different entities composing your application.
Contexts are a feature that will eventually be released in React.js - however, they exist today in an undocumented form. I spent an afternoon looking into the present implementation and was frustrated by the lack of documentation (justified, as it is a changing feature). I've pieced together a few code examples that I found helpful.
In React.js a context is a set of attributes that are implicitly passed down from an element to all of its children and grandchildren.
We’re going to build a Q&A system from scratch starting off with setting up your project using Yeoman and outlining the structure. Along the way we’ll talk about custom elements, material design, routing, authentication, security rules, and record priority. Users will be able to write questions, answers, and comments. Both questions and answers can be upvoted. Using security rules, we’ll make sure that users can only manage their own content within Firebase.
This is an ambitious blog post with a lot of code. If you find an error or aren’t sure how to continue, leave a comment in the post and I’ll make improvements. Walking through this entire series (in progress) could take an hour or two, but by the end you’ll have a thorough understanding of how to build a basic Polymer app.
Google’s success at making the OS available at lower price points means that many users have devices with relatively limited performance. Giving those users a good experience is vital. Here are some lessons I’ve learned while optimising my App to look good on older or slower devices.
Over the course of the next few years, the way we code is going to change in radical ways, pushing us in a fundamentally different direction than the one we’ve been sprinting for the past 30 years or so. These changes will lead to many important breakthroughs in programming techniques, processes, application scalability, and quality controls.
A couple of months ago, I learned React by writing a game called Flip. Since then, React and the Flux architecture have attracted a lot of attention in the web developer community. Because of React’s superior DOM performance, and the scalable nature of Flux’s one-directional data flow, many in the industry suspect that React+Flux may become the “next big thing” in front end web development.
Facebook doesn’t provide a framework for Flux, only how to make one from scratch. So I began searching for implementations. Surprisingly, there are already a few good (though somewhat poorly-named) options: jFlux, Fluxy, Fluxxor, and finally, Reflux. Of them, Reflux appeared to have the most backers and the most elegant API. I was also won over by Krawaller’s explanations of the overarching philosophy behind Reflux and how using Reflux can dramatically simplify a Flux application.
A brief journey into reactive interfaces with FRP and React.js
In this post, I will discuss the way we approach building interfaces with reactive programming and React, and how it’s changed the way we think about writing effective code. The first half will cover how we use reactive programming — RxJS, more specifically — to compose our data sources, and the second will talk about feeding that data into React.
* Introduction Browser and Node.js Compatibility Who This Book is For Overview Help and Support * The Basics Better Unicode Support Other String Changes Other Regular Expression Changes Object.is() Block bindings Destructuring Assignment Numbers Summary * Functions Default Parameters Rest Parameters Destructured Parameters The Spread Operator The name Property Block-Level Functions Arrow Functions Syntax Summary * Objects Object Categories Object Literal Extensions Object.assign() Duplicate Object Literal Properties proto, Object.setPrototypeOf() super Reflection Methods Summary * Iterators and Generators What are Iterators? for-of Generators Built-in Iterators Advanced Functionality Summary * Symbols Creating Symbols Identifying Symbols Using Symbols Sharing Symbols Finding Object Symbols Well-Known Symbols Summary
Here at Viget, we've become huge fans of React. It gives us greater flexibility by working with a virtual representation of the DOM. When the DOM simply becomes an idea, instead of a requirement, rendering becomes just another implementation detail. This is particularly useful when rendering content server-side, loosely diagrammed below...