Instead of showing a Yes/No prompt before deleting a comment, delete the
comment right away and replace it with link to undo the delete action.

This was easy to accomplish as we never delete the comments, but just
mark them as deleted in database.

The same HTML was created in two places. Now it's in single spot at
Docs.view.Comments#getPagerHtml.

The HTML is now also more straight-forward, allowing us easily to
display either link or plain text inside the pager container.

It's helpful to know how many comments there are in total.
Previously you didn't see the total count when there was < 100.

This stopped working after switching to MongoDB, as the recent_comments
query no more returned the total_rows and other parameters needed for
creating the "Load more..." link.

Also fixed the "Load more..." link to always show the nr of comments
that are to be loaded.

Previously the comments idMap didn't contain the static members at all,
so when new comment was posted, its target was set to ["unknown"].

Rename some functions to better reflect what they do:

- sanitize --> markdown
- formatComments --> scoreComments
- getCommentsMeta --> getCommentCounts

Just helpful when starting up the server for the first time.

There was an opts parameter which attempted enabling sencha.com/* URL-s,
but this option wasn't used anywhere the function was called from -
besides the option didn't work because some code before it attempted
turning all URL-s into links, but mistakenly also picked up URL-s
within href="...".

Anyway, I see no reason to only allow links to sencha.com, so allowing
all links, whatever they may be.

The code for convering URL-s to links is not needed at all because the
'marked' module does this already.

Because overrides can be circular (Notably Ext.Base#destroy),
store into overrides array just the name,owner,id of the overridden
member, not the member hash itself - previously we stored the
actual member hash, which in case of circular overrides resulted
in infinite loop when serializing the class into JSON.

Fixing a regression introduced by sorting instance and static members
intermixed.

There's too much happening in DocFormatter, moving these things
to separate classes, will make it a little bit cleaner.

For now implementing two types:

    {@video html5 some/url.mpeg Comment...}

    {@video vimeo 8791231354 Comment...}

With future possibility of allowing users define their own types.

This allows easy embedding of videos to guides (and even to class
docs if there should be such need).

For now only supporting Vimeo videos, just like the separate videos
page:

    {@video <vimeo-video-id> Some comment}

Previously when class Foo happened to be listed before Foo.Bar,
the Foo node was created and Bar added as a child to it, but
Foo was left to be a leaf node, which meant its children were
invisible, making the class-tree look broken.

To please our asian fellows.

Previously it may have happened, that multy-byte characters got
breaken from the middle, resulting in invalid characters. Now
we're using the unicode support in regexes to count chars correctly.

A great resource for UTF-8 support in Ruby 1.8.7 is found here:
http://blog.grayproductions.net/articles/bytes_and_characters_in_ruby_18

Also remove some useless comments.

The search no more assumes we are dealing with classes and members.
We just supply the short and full name of an item, whatever it is.

A first step in making possible to include guides and other stuff
to search.

Exposed Docs.History#navigate method to have an easy way to navigate
to any page by URL.

Having a notification makes it obvious that something happens right
when clicking the checkbox.  Otherwise one has to wonder if he needs
to post a comment for the checkbox to take effect.

The extjs/ subdir in JSDuck output is now dedicated to the ExtJS
which the Docs app itself uses.

For examples to work, a separate directory (by default extjs-build/)
should be created and referenced from eg-iframe.html and examples.

Instead of hardcoding ExtJS and Touch examples paths, the
--examples-base-url option determines where icons are located.

The important change is that examples.json file now has to define
icons relative to --examples-base-url (this was the case for Touch,
but not for ExtJS).

Example title and description fields are now also correctly convered,
independent of url being absolute or not.

Auto-created example name no more contains the --examples-base-url
in it.