Now raw data is gathered on the backend and rendered on the frontend.

This validates application name asynchronously on the server. Validation is synced with namespace select :)

- See issue: https://github.com/kubernetes/dashboard/issues/76

They just have been recently added. It allows us to delete some code.

This is because new compiler version has new type inference, which is
more strict.

The UI is as specified in the mocks, except for the names of the fields.
I decided to go with what is in the API.

Everything is extensively tested. I also added some tests for previously
untested cases.

Added check to prevent display of replica set list page when there are no replica sets.

This change handles replica set description end-to-end: saving in on the
deploy form and then displaying. It also handles replica set endpoints.
I also attempted to write tests for the go code, but this change grew
too much. I'll do this later.

With this change I've gone through all ESLint rules at:
http://eslint.org/docs/rules/ and added all of them that I feel make
sense to the project.

This will allow us to focus on business logic of our code, rather than
on style discussions, which are now better guarded thanks to ESLint and
clang-format.

On the final note: it does not matter what concrete lint rules are
enforced (e.g., semicolons or nor). The important part is that they are
enforced by a tool and we do not spend time dicussing about them.

Addresses: #66

This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

The implementation consists of backend code and sample frontend view
that dumps the data into an ugly looking table. Subsequent changes will
implement frontend so that things look pretty.

The cards now display mostly fake data, but they look more complete. The
backend will be implemented soon.

Per discussion in: https://github.com/kubernetes/dashboard/issues/65

This change does only renaming, no functional modifications.

This is to show in a simple layout what the backend returns.

Based on mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/08_deploy%20form.png

This change implements both backend and frontend for the view. This is
the approach I'll follow in the future.

This is a simple end-to-end implementation for to make sure that the setup works.

This change modifies a lot of JS, but this is only to prove that the
code works. Later changes will cleanup the JS more.

With this change advanced optimizations of the Closure Compiler work and
produce working output.