Instead of generating the background images with `secha slice`
just disabled them and defaulting to background color.

Looks much better now.

It should also work for IE, but haven't tested.

As all exports are in JSON format, it doesn't make sense to have
one export type called "json". The name "full" describes it better.

Renamed JsonExporter to FullExporter accordingly.

The Exporter performed two different tasks, which are now
better divided between two classes.

JsonPExporter is now AppExporter - the purpose of it is to
generate data for docs app, the actual format is decided by
ClassWriter.

Exporters now only deal with generation the data, ClassWriter
decides whether to write it into .json or .js files, or to STDOUT.

This is similar to json export format, with the difference that
only class and method names are included to exported JSON.

Added two classes:

- JsonExporter - exports single class to JSON format file.
- JsonPExporter - exports single class to JsonP format file in compact form.

Additionally one can now use: --output -
This will produce output to stdout.

Old --json    is now  --export=json
Old --stdout  is now  --export=json --output=-

The TemplateDir is now only responsible for copying or linking
the tempate directory.

It takes care of the creation of data.js file.

Didn't quite work out this way. Instead now separating out the
different tasks in output. For start the source code export is
now fully done inside SourceWriter class, which got a write_all
static method.

The main chunk of the normal HTML output is done by TemplateDir
class that at the moment does a bit too many things.

Splitting the output routines into three classes:

- StdoutExporter
- JsonExporter
- HtmlExporter

Additionally creating ClassWriter class for outputting the .js or .json
files. This one isn't pretty, but I have to share the output logic
between JsonExporter and StdoutExporter.

Another nastiness is the format_classes method which has to run BEFORE
writing out classes JSON, but AFTER the source HTML files have been
created - because of the parallel stuff. Brr...

At least the App class now has less responsibilities, but further
refactorings are needed.

Welcome, Guides, Videos, Examples and Categories now all have a
static #create method to be used instead of #new for instantiation.

The #create returns either the corresponding object instance or
NullObject which behaves as if it were the needed object, but
effectively does nothing.

Categories.create is a bit different - it first uses one of two
strategies for creating categories: FileCategories when filename
present or AutoCategories when not, then feeding the resulting
categories list to actual Categories object.

Somehow it was missing in when doing stdout export while it
was nicely present in standard json export. Probably I forgot
to add it there by myself.

- words in class header.
- sum of words in all class members.
- average nr of words per class member.

Separate stats for all the different member types.

Taken from:
http://blog.typekit.com/2011/05/25/loading-typekit-fonts-asynchronously/

This should take care of the problem of docs app freezing for almost
a minute before failing to load TypeKit font.

Original MDC docs listed 4 parameters - it's more accurate to list two,
both of which can be of two types.

Handle case when Docs.data[something] is undefined - previously
we expected it always to be an array.

The #m-comments had been left unreplaced with .comments-section

It felt like something is broken, because links were missing.
Then I discovered that the links just don't appear fast enough.

I see no reason to artificially slow users down. I want to scroll
down to the damned method and click view-source as fast as I can.

I had to click too many times more-more-more to get at the end of the
list.

This has been made redundant by including word-count metric to
stats module.

Turned on with --stats option, a new static tab appears that
shows various statistics per class. For now there's just a table
that lists:

- nr of members
- nr of non-inherited members
- fan-in
- fan-out

This way we can either loop or map or reduce over the items as we
wish. Plus the method name is more clear in what it does.

Also added #all_members - method which does the same but includes all
the inherited and mixed in ones.

Fixes the issue of web servers that can't handle double-slashes //
in URL-s.

Show the tab only when user is logged in as moderator.

Renamed CSS class 'comments' to 'comments-div' to avoid conflict with
styles to the static tab, which mush have class 'comments'.

When you brush over the hover menu with the mouse on your way somewhere else it can be annoying that the hover menu shows.

For example:

    /** @class Parent */
      /** @method foo */

    /** @class Child @extends Parent */
      /** @method foo @private */

Previously this resulted in Child class docs having method foo from
Parent, as if the private foo in Child didn't exist at all.  This
behavior was quite far from obvious.

Now the Child class docs will have no foo method at all - the parent
class method gets shadowed with @private foo in subclass.  This should
be more like what the documentation author intended.

As a bonus we now have better error messages for cases where {@link}
refers to a private member, and @inheritdoc can be used to inherit
docs from private members.

Previously it was only checked if IE >= 8, but now we do proper
feature-detection. This also disables comments in Opera, so Docs
app no more crashes it.

Also we now hide the comment controls completely when comments
are disabled. Previously the view-comments buttons were still there
when comments were disabled.