This way when CSS or JS changes, the URL-s of those files will change
too, ensuring that that those files won't be read from cache when
docs are generated with new JSDuck version.

Previously the counter showed the count from previous load.

The relative positioning gave unstable results. Switching over to
using floats and line-height.

For some reason I don't manage to get the loading of build-js.html
file to work.

A typo in variable name.

Drop the temporarily used /session_new.

Created TopLevelDropZone to handle dragging to the sidebar
of comments expander.

Dropping comments on another comments now actually does the request to
backend, changing the parent of the comment, and then reloads the whole
list of comments.

This is the implementation of just the visual side of dragging.
Everything that happens after the drop is still unimplemented.

An expander component with nicer styling which doesn't distract as much.

It somewhat duplicates the functionality of the old Expander, but then
again it behaves different enough.

Only trigger the action when the click happens in current view,
not in the subview.

For now it's somewhat buggy, throwing errors here and there, but
the essential functionality works.

This way the comments server will decide how and where the registration is
performed.

As it doesn't close the currently active tab.

Again, to keep the root of jsduck repo cleaner.

To keep the root dir cleaner.

The comments server is now available at:

    https://github.com/senchalabs/jsduck-comments

The comments server is quite a separate app so it's better maintained
as a completely separate project.

This should take care of the occasional problem in comments server
when it from time-to-time goes down because of a slight glitch in
MySQL connection.

This didn't caused problems because the InlineWrap isn't a component.
But it generated a warning.

Various classes were not directly listed with the requires statement.

Additionally Sencha command complained about being unable to find
Ext.JSON, so excluding this, as it's within the ext core anyway.

It was moved before the other scripts to ensure that comments
enabling code is included before docs app code, but new that the
comments code is withing data.js, that's no more needed.

Now one can simply use these options instead of injecting special
comments-enabling JavaScript with --head-html.  The JavaScript side
is now also better as it accesses the commentsUrl and commentsDomain
properties of Docs.data object, not a lot more properties on the
root Docs object.

This way it's apparent to the user of the site why he gets served
with a particular version.

Instead of using the server-side PHP script, the browser detection
is done one the client side with a compact JavaScript snippet taken
from http://detectmobilebrowsers.com/

This allows the index page of the docs to be cached, lowering the
burden on servers.

Instead of crashing mysteriously, the circular @mixins and @extends
now result in fatal error message which clearly shows the
dependency chain that's causing the problem.

Move {head_html} before the app.js.

This way the comments settings will be available before
the rest of the app is loaded, especially the CommentsProxy which
assumes the Docs.comments* settings to be available.

Default Docs.Comments#getCount to return 0 when comments aren't enabled.

The monsterid was a bit too silly. Docs seem to require something
a bit more formal.