Take care of the toggling of comments help inside the form.

Nothing more for start.

Only turn properties into configs when dealing with autodetected members.

The validation relied on user_id field being available in comment
data, but this field was in fact missing, resulting in the comment author
to never equal current user.

Handle the whole voting logic inside comments.List view.

Not yet working, but fires event when clicked and displays the
correct info.

Move the old Comments controller aside and write a new simpler one
that for now only manages the comments index page.

Had gone missing with some previous refactoring.

Comments get rendered through the comments.List view.

Change Docs.Application to initialize comments before anything else.
This way the rest of the app can rely on comment counts to be
already loaded and avoid setting up listeners all over the place.

Additionally the CommentCounts is now accessed through Docs.Comments
and never directly as it's no more a singleton.

The Docs.Auth is now observable and fires an "initialized" event
after it's been set up.

Created Docs.Auth which performs the actual login/logout stuff.
Docs.view.auth.Form represents the form at the header of the app,
firering "login" and "logout" events.

The Auth controller just binds these two things together - listening
to the events from AuthForm, performing the login with Docs.Auth
and calling back to AuthForm to change how it looks after login.

Didn't really succeed fully as other stuff in Comments controller
also depends on calling the openComments and closeComments methods.

Crap.

Forgot to rename selector in controller.

This will take care of rendering the comments expander together with a
large heading "Comments".  Use in the main comments section of class
and in guides and videos.