gaearon

/** @jsx React.DOM */
'use strict';

var React = require('react'),
    { PropTypes } = React;

var AudioPlayer = React.createClass({
  propTypes: {
    source: PropTypes.string.isRequired,
    isPlaying: PropTypes.bool.isRequired,

thomasboyt

I've been struggling to come up with a good pattern for handling loading state in Flux (specifically using Fluxxor, though I think this is an issue for any implementation).

When I say "loading state," what I mean is state in a store that tracks:

• Whether the data handled by the store was loaded
• Whether the store is currently attempting to load data
• Whether the data loaded successfully or errored
• The error message, if it errored

Here's my first (very simple) pass at this, a store mixin called LoadingStoreMixin.js:

roycehaynes

var AppConstants = require('../constants/AppConstants.js');
var AppDispatcher = require('../dispatchers/AppDispatcher.js');
var api = require('../utils/api');

var ActionTypes = AppConstants.ActionTypes;

module.exports = {
  create_customer: function(data){
    api.customer.create(data);
  }

Rplus

伸縮自在的愛

using svg automaticly generate fonts by gulp-iconfont

這篇主要是要講如何使用 SVG 圖檔來生成 icon font，
並且要讓這 icon font 能順利在 CSS preprocessor tool 下接軌

目前 github demo repo 是使用 stylus preprocessor

martinklepsch

(ns creator.core
  (:require-macros [cljs.core.async.macros :refer [go]])
  (:require [om.core :as om :include-macros true]
            [cljs.core.async :as async :refer [chan <! >! put!]]
            [om-tools.core :refer-macros [defcomponent]]
            [cljs.reader :as reader]
            [goog.dom :as gdom]
            [om-tools.dom :as dom :include-macros true])
  (:import [goog.net XhrIo]))

john2x

Clojure Destructuring Tutorial and Cheat Sheet

(Related blog post)

Simply put, destructuring in Clojure is a way extract values from a datastructure and bind them to symbols, without having to explicitly traverse the datstructure. It allows for elegant and concise Clojure code.

Vectors and Sequences

evancz

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

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.

---

jlongster

(function() {
  // Do not use this library. This is just a fun example to prove a
  // point.
  
  var Bloop = window.Bloop = {};

  var mountId = 0;
  function newMountId() {
    return mountId++;
  }

jasonLaster

  var AnimationRegion = Backbone.Marionette.Region.extend({

      innerRegionSelector: '.inner-page-region',

      setLayout: function(layout, animationClass) {
          this.regionAnimationClass = animationClass;

          if (this.currentLayout) {
              this.swap(layout);
          } else {