I think it's not compiling/jsxTransforming/browserifying properly.

1. Asana or Waffle
2. Git strategy- rebase?

Warning: Something is calling a React component directly. Use a factory or JSX instead. See: http://fb.me/react-legacyfactory
main.js:19632 Warning: App is calling a React component directly. Use a factory or JSX instead. See: http://fb.me/react-legacyfactory

Found this resource, which appears to be straightforward: https://gist.github.com/sebmarkbage/ae327f2eda03bf165261

But currently unable to find the guilty code. It should be in the general js folder or the components folder.

Add to the comments that the POST requests for moving files should include the locations/directories within services of both where the file is moving to and where it's coming from

MVP is to just be able to drag and drop files. MVP may not include being able to open the files. This is a high priority item after fundamental functionality.

1. build out linkages in appConstants.js
2. Update appActions.js according to the notes in there
3. the boilerplate dispatcher uses es6 promises. see if we should refactor to be consistent with other promises.
4. Serve static files from server

it might be doing this already- if so, it's an easy win for us!

it is the ultimate data store.

we're trying to just update the store

every component has it's own state and props attributes.

this.state.whatever sets the immediate variables the store has access to, but those variables don't have access to the store. those variables have access to parent variables.

Specifically a list of files. That's the only thing we care about right now.

React/Flux does not have a router. I have received suggestions to use the Backbone router to move between Signup, Login, and Main Page

Specifically, a list of files. That is the only thing we care about right now- just any list of files.

Search will exist only within the file lists the client already has. This will not make any API calls to our server.

Not sure if we should have it show/hide the div or add/remove div.
This might be a good resource:
http://facebook.github.io/react/docs/animation.html

Many of the store's methods must return objects for output to the components (or else a serious error is thrown), but these return statements won't take object literals. They're going unrecognized right now.
In order to get the pages to render, I have references to the store commented out until this is fixed

1. the flow through the react/flux architecture
2. the build process- i've built out my understanding of it
3. where to find the files in our secrets folder
4. any important learnings or hacks from our integrations with each api

The Drive API getAllFiles may not work when the contents of the drive being retrieved is too deep. My guess is that it has something to do with timeouts being set. The function may need a more efficient algorithm.

I laid out the structure of the wiki tonight. Let's use it to have the most awesomely documented codebase in the tri-desk area!

1. Get file lists from both services.
   Send:
   Type: Get
   data:getAllFileLists
   Receive: json file lists, where both file lists are in the same format
2. Move file from one location to another
   Send:
   Type: Post
   data: fileID, fromLocation (path most likely), toLocation (again, a path most likely). fromService (service name), toService (service name)
   Receive: fully updated file lists from each service. This will be the complete file list from each service to start with.
3. Signin and authetication
   Send:
   Type: Post
   data: username, password. This will look up the tokens for each service in the database.
   Receive: authentication stuff.
4. Signup
   Send: username
   Receive: if that username is available/fits our requirements
   Send: username and password for CloudBalance
   Receive: authentication stuff
   Send: oauth info for both services
   Receive: more authentication stuff.