Justin Ip ippy04

The introduction to Reactive Programming you've been missing

So you're curious in learning this new thing called (Functional) Reactive Programming (FRP).

Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:

Rx.Observable.prototype.flatMapLatest(selector, [thisArg])

Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.

Settings

Create a project in XCode with the default settings
- iOS > Application > Single View Application
- Language: Swift
Under project General settings, add ReactKit to Linked Framework and Libraries
- + > Add Other... and choose /path/to/react-native/ReactKit/ReactKit.xcodeproj
Now ReactKit would have been imported. Link it by choosing it from the list.
- + > lib.ReactKit.a
Under project Build Settings,

WebSockets + Reflux + React

Using WebSockets, React and Reflux together can be a beautiful thing, but the intial setup can be a bit of a pain. The below examples attempt to offer one (arguably enjoyable) way to use these tools together.

Overview

This trifect works well if you think of things like so:

Reflux Store: The store fetches, updates and persists data. A store can be a list of items or a single item. Most of the times you reach for this.state in react should instead live within stores. Stores can listen to other stores as well as to events being fired.
Reflux Actions: Actions are triggered by components when the component wants to change the state of the store. A store listens to actions and can listen to more than one set of actions.

3rd-party image processing/manipulation services

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Product/User Definition

How are you understanding customer needs?
What are the top things users want?
Where do new users come from?
Who is going to be your first paying customer?
What resistance will they have to trying your product and how will you overcome it?
How does your product work in more detail?
How will customers and/or users find out about you?
How are you meeting customers?
What do you understand about your users?

	require 'sinatra'
	require 'redis'
	require 'json'
	require 'date'

	class String

	def &(str)
	result = ''
	result.force_encoding("BINARY")

	# # your config.ru
	# require 'unicorn_killer'
	# use UnicornKiller::MaxRequests, 1000
	# use UnicornKiller::Oom, 400 * 1024

	module UnicornKiller
	module Kill
	def quit
	sec = (Time.now - @process_start).to_i
	warn "#{self.class} send SIGQUIT (pid: #{Process.pid})\talive: #{sec} sec"

	#!/usr/bin/env bash

	if [[ ! ( # any of the following are not true
	# 1st arg is an existing regular file
	-f "$1" &&
	# ...and it has a .ipa extension
	"${1##*.}" == "ipa" &&
	# 2nd arg is an existing regular file
	-f "$2" &&
	# ...and it has an .mobileprovision extension

	# This is not a ready-to-run script. It just shows the relevant command-line calls.

	XC_WORKSPACE=path/to/MyApp.xcworkspace
	XC_SCHEME=MyApp
	XC_CONFIG=Release
	ARCHIVE_PATH=dest/path/to/MyApp.xcarchive
	EXPORT_PATH=dest/path/to/MyApp.ipa
	DIST_PROFILE=NameOfDistributionProfile

	# Build and archive. This can be done by regular developers, using their developer key/profile.