Jason Block jblock

## index.html
<!DOCTYPE html>
<meta charset="utf-8">
<style>

</style>
<body>
<script src="http://d3js.org/d3.v3.min.js"></script>
<script>
var width, height;

## Because twitter is bad for this.md

      
              1 file
            
          
              0 forks
            
          
                2 comments
              
            
              0 stars
            
          
                jblock
                / Because twitter is bad for this.md
            
            
              Last active
              August 29, 2015 14:14
            
              
                React Native question
              
          
    We all got really excited about React Native (both our mobile and our web people), but we don't have anywhere near the people-nhours needed to use it as our primary way of making views on mobile (at least not yet).
One idea that myself and some others had, though, was to utilize it as a data layer that we could share across our mobile and web platforms as we start to stabilize our APIs, with the native developers still making views in UIKit and Android in the interim.
Hence why I was asking if there was some way to have a top-level React component that would allow us to communicate with the React Native runtime (apologies if I'm using the wrong words to describe it here). That way we could share Flux stores/API endpoint specifications between these different platforms as needed.
Does that make any more sense? I also know that it goes a bit against the whole "learn once, write anywhere" thinking you all talked about at the conference.

  
## stuff.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                jblock
                / stuff.md
            
            
              Created
              February 16, 2015 02:00
            
              
                React Presentation
              
          
    Trunk Club React.js 101

First part


Disclaimer:

Gonna use regular JS: semicolons, function(), and vars
Not gonna talk about higher-level tools, data gathering, etc.

Gonna focus on just React. because this is a 1 hr lesson.


What you're gonna get out of this:

You'll be able to look at a React Component without crying


You'll be able to take a piece of data and turn it into an interactive thing


## gist:b70dcd5ee54313fa9137
### Keybase proof

I hereby claim:

  * I am jblock on github.
  * I am jasonblock (https://keybase.io/jasonblock) on keybase.
  * I have a public key whose fingerprint is 2694 6B5A 445A A9CD 28DB  67DC 704A 3203 2CB9 B96A

To claim this, I am signing this object:

## SketchSystems.spec
LandscapeHub Orders
  cancel -> cancelled
  draft*
    submit -> submitted
    submit_for_review -> needs_review
  submitted
    send_purchase_order -> purchase_order_sent
    submit_for_review -> needs_review
  purchase_order_sent
    confirm -> confirmed

## SketchSystems.spec
draft*
  submit -> submitted
  submit_for_review -> needs_review

LandscapeHub Orders
  cancel -> cancelled
  submitted
    send_purchase_order -> purchase_order_sent
    submit_for_review -> needs_review
  purchase_order_sent
	<!DOCTYPE html>
	<meta charset="utf-8">
	<style>

	</style>
	<body>
	<script src="http://d3js.org/d3.v3.min.js"></script>
	<script>
	var width, height;
	### Keybase proof

	I hereby claim:

	* I am jblock on github.
	* I am jasonblock (https://keybase.io/jasonblock) on keybase.
	* I have a public key whose fingerprint is 2694 6B5A 445A A9CD 28DB 67DC 704A 3203 2CB9 B96A

	To claim this, I am signing this object:
	LandscapeHub Orders
	cancel -> cancelled
	draft*
	submit -> submitted
	submit_for_review -> needs_review
	submitted
	send_purchase_order -> purchase_order_sent
	submit_for_review -> needs_review
	purchase_order_sent
	confirm -> confirmed