One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
// Module dependencies | |
var express = require('express'), | |
mysql = require('mysql'); | |
// Application initialization | |
var connection = mysql.createConnection({ | |
host : 'localhost', | |
user : 'root', |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
doctype html | |
/[if lt IE 7] | |
| <html class="ie6"> | |
/[if IE 7] | |
| <html class="ie7"> | |
/[if IE 8] | |
| <html class="ie8"> | |
/[if IE 9] | |
| <html class="ie9"> | |
| <!--[if (gte IE 9)|!(IE)]<!--> <html> <!--<![endif]--> |
// -------------------------------------------------------------------------------------- | |
// A More Modern Scale for Web Typography | |
// Based on this article: http://typecast.com/blog/a-more-modern-scale-for-web-typography | |
// -------------------------------------------------------------------------------------- | |
$body-font-size: 1em !default; | |
// Adjusts body typography to be default | |
// for each browser. | |
@mixin reset-body-font-size($size: 100%, $size-adjustment: 0.5) { |
hfsevents > configure | |
hfsevents > Configuring hfsevents-0.1.6... | |
hfsevents > build | |
hfsevents > Preprocessing library for hfsevents-0.1.6.. | |
hfsevents > Building library for hfsevents-0.1.6.. | |
hfsevents > [1 of 1] Compiling System.OSX.FSEvents | |
hfsevents > | |
hfsevents > /private/var/folders/mz/qg5255493sx8rjpd1t9fwll00000gq/T/stack-893b4ee60c20394e/hfsevents-0.1.6/In file included from cbits/c_fsevents.m:1:0: error: | |
hfsevents > | |
hfsevents > /private/var/folders/mz/qg5255493sx8rjpd1t9fwll00000gq/T/stack-893b4ee60c20394e/hfsevents-0.1.6/In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23:0: error: |
This is a full-day workshop on intermediate to advanced topics on building real-world ReactJS Web applications. We will start by learning about the core fundamentals of Redux including pure functions, actions, reducers, the store, and subscriptions. Then we will integration Redux into a React app, learning about components vs containers, accessing the store, async actions, middleware, and thunks. Next, we will layer in React Router 4, learning about params, queries, and redirects; prompt before navigation, and scrollToTop.
Time permitting and based on audience preferences, we can learn about using component libraries, styling, forms and validations, and more!