Add the UI to view and buy tokens

[come-maiz]

Requires #5

[frangio]

This same action is being dispatched in the ValidateMe component. I think we should only dispatch it once. Then, in Wallet for example, we should have a componentDidUpdate method where we check if this.props.address !== prevProps.address, and if so we dispatch getBalance.

[frangio]

And the only time it should be dispatched should probably be in a component upper in the tree. I am reminded of react-web3 where there is a Web3Provider component wrapping the rest of the application which provides and updates the accounts. I would like us to try that library but we can do with a simpler thing for now.

[frangio]

Are we planning to use mapDispatchToProps as was recommended in another review?

[come-maiz]

I did mapDispatchToProps in #8.
I will try moving findAccount higher, and I reported #10 to experiment with react-web3.

[come-maiz]

ok, I added Account.react.js, which is now the only one who gets the account. @frangio please take a look to see if it's good enough while we get react-web3.

[frangio]

This is good. I think the Account component should be a parent of all the other components that use the address. This is how Web3Provider works, and I think this is in general the "Provider" pattern.

What we have now is good enough though.

[frangio]

I haven't tested this on my machine yet but let's move forward.

[come-maiz]

I thought about making it a parent. Just a little, not much. And it seemed to me that because we share the store everywhere, the hierarchy doesn't matter much. I will dig more when using the Web3Provider, but this makes me think that it's also not important where you put it: https://www.npmjs.com/package/react-web3#redux-support

Thanks again! I hope that getting less things to fix from you means that I'm getting the hang of this, and not that you are getting tired ;)

merging...