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.

Moved bunch of code away from the humongous Docs.view.Comments.

The emailHash of user wasn't sent when user logged in.

Add note about replying to other people.

Attempt making the syntax help more visible.

Add a new version with a different name alongside it.

This way we can keep two versions of the API working at the same time,
which is needed when first deploying the backend code and then waiting
for the frontend code to get moved into live.

Added field to the top of both users and topics which allows filtering
the lists below them.

Every time the filtering happens, the previously existing selection is
cleared.  This is maybe not the best behavior, but that's the compromise
I arrived at to prevent several edge-case bugs.  The problem is, that
when you filter out a currently selected record, it becomes deselected,
but the deselect event doesn't fire to let us know...

Only remember the sorting order of comments page until next browser
refresh.

Now only the hideRead is remembered across sessions (and that's a
moderator-only setting).

Settle to a nice camelCased naming scheme.

Replacing the magic color value scattered around in code.

Created HeaderMenu class that provides the UI for switching.
Allow only user or topic to be selected (not both together).

For start show the list in place of users list.

When switching from "users by vote" to "users by comments"
select the previously selected user.

This was only useful for moderators before all the comments of
moderators were automatically marked as read.

Allow selection of user from users list and then filter the comments
list to show only comments of that user.

The selection of user is not saved into settings, but is stored until
the next page refresh.

With the sole responsibility of providing a way to perform
queries to the comments backend.

Let links be blue as they should be.
Hide the member type info from link - it's not that important.

Now the tab panel of users list makes sense.

The page is now also visible to normal users, with the only difference
that hideRead checkbox is only shown for moderators.

The page is divided into two sections: comments & users.

The comments section has two tabs which determine how the comments are
sorted (instead of a checkbox determining it).

The users section has a list of all users sorted by votes.

Store the session cookie also when user is not logged in - just to keep
his session ID and not create a new session for each and every request.

Additionally use Ext.JSON instead of JSON.

Previously the receiver of comment was used in place of the actual
author.

The latest 3.0.0rc4 release broke JSONP requests handling.
Additionally I'm getting some strange 404 errors.

This was to just try out some queries.
Most of them have now been implemented.

Instead of dropping and recreating the database we now drop all the
tables and then recreate them.  This is because in our staging server I
currently have just one database available and I can't drop and recreate
it to run tests in it.

Additionally eliminated the update_votes.sql script - the triggers
themselves take care of votes being calculated.