rt2zz

 
Site hosted by Angelfire.com: Build your free website today!

January 27-28, 2001


B and I were both excited to get back into the cave and get to work. I figured with about 4 hours work we could be in and see what was on the other side. We had arranged to borrow a DeWalt cordless drill to bring with us. We also had masonry bits to drill with, sledge hammers (two) to break up the rock, bullpins to insert into the drill holes, and a few other tools that we ended up not using. Getting the tools down to the work site proved to be a challenge. One of us would climb down the rope and stop at a ledge or good resting place, then the other person would lower the tools. We kept repeating this routine until we got to the bottom of the cave. Then we had to drag the tools to the hole. It took about an hour to finally get to work. 

B took the first turn at the hole. After an hour of exhausting work we could tell that we were not going to get through in one session. We kept trading off after we worked ourselves into a s

rt2zz

 
Site hosted by Angelfire.com: Build your free website today!

I will divide the text into two colors for the sake of clarity. The gray text is taken directly from my caving journal. The italicized blue text is my comment as I reflect on the experience. I will do my best to convey the thoughts and feelings I had during the entire event. I will not use the actual names of the other individuals involved. I will include the entire relevant text of my journal. Only small parts of the journal will I skip. This will only occur when the entry has nothing to do with the experience in the cave, such as eating dinner after a trip, getting fuel or snacks, irrelevant details, etc. (My journal is fairly thorough) I will merely summarize what I am cutting out of the actual entry.
In an effort to present this experience in as accurate light as possible I will type my journal as I wrote it: sans grammar check. Please overlook my errors. My additional comments will help to clarify the things I wrote in my journal. 


Caving 

rt2zz

 
Site hosted by Angelfire.com: Build your free website today!

I will divide the text into two colors for the sake of clarity. The gray text is taken directly from my caving journal. The italicized blue text is my comment as I reflect on the experience. I will do my best to convey the thoughts and feelings I had during the entire event. I will not use the actual names of the other individuals involved. I will include the entire relevant text of my journal. Only small parts of the journal will I skip. This will only occur when the entry has nothing to do with the experience in the cave, such as eating dinner after a trip, getting fuel or snacks, irrelevant details, etc. (My journal is fairly thorough) I will merely summarize what I am cutting out of the actual entry.
In an effort to present this experience in as accurate light as possible I will type my journal as I wrote it: sans grammar check. Please overlook my errors. My additional comments will help to clarify the things I wrote in my journal. 


Caving 

rt2zz

scale x by 2
[2 0 0 0
 0 1 0 0
 0 0 1 0
 0 0 0 1]
 
scale y by 2
[1 0 0 0
 0 2 0 0
 0 0 1 0

rt2zz

// require something
var im = require('immutable')

var a = im.List(['a', 'b'])
var b = im.List(['a', 'c'])
console.log(a.toArray())
console.log(b.toArray())
console.log(a.merge(b).toArray())
console.log(b.merge(a).toArray())

rt2zz

##Thoughts on flux, actions, and doing work in a Flux app

Reference for what I am considering to be "conventional" https://github.com/facebook/flux/tree/master/examples/flux-chat/js

###Many Files This the conventional scheme uses an action flow that goes from Component -> ActionCreator -> APIClient -> ServerActionCreator Problems

• Implementing request/response API call requires edits on 5 files Constants, ActionCreator, APIClient, ServerActionCreator, Store
• ServerActionCreator methods are almost always passthrough boilerplate

rt2zz

animation v transition v (?) genisis transition 
genisis transition should be domful
animation should be statelful
thumb swipe is animation
genisis transitions are simpler abstraction, less control, meant purely for visual sugar

idiomatically transitions operate on different nodes than animations. 

transition element takes in manifest triggered by parent using method..transition('type', cb) 

rt2zz

// OPTION A - Current Setup
// Logic/Control in Action
Component.componentWillMount = function(){
  AccountActions.updateAccount(data)
}

Client.updateAccount = function(data){
  apicall(data, function(data){
    AccountServerActions.updateAccount(data)
  })

rt2zz

// require something
var _ = require('lodash')
var news = _.merge({a: [1]},{a: [2]})
var news2 = _arrayMerge({a: [1]},{a: [2]})

function _arrayMerge(obj1, obj2){
  return _.merge(obj1, obj2, function(a, b) {
    return _.isArray(a) ? a.concat(b) : undefined;
  })
}