Because the font-set is only registered for sencha.com and localhost,
running the docs app at any ther domain will get 403 error when
attempting to load fonts from typekit.com.

We should probably completely move this code to sencha-specific config
files.

Those files haven't existed for ages.

Forgot to update version number printed by --version.

Because {Type=} defined an optional item, it was taken granted that
just {Type} would define a required item.  Not so fast - while
params default to being required, configs default to being optional.

Makes it easier to find the close-all-tabs feature.

Handling the internals of tabs inside the view and leaving the
handling of higher-level events to the controller.

It makes sense for the tabs component to adjust itself when it's resized,
rather than having a controller tell it.

Monitor the clicks on menu items inside the view.

This way the whole interaction with tab-menu is entirely encapsulated inside view.

Instead access the menu from this.overflowButton.menu.

Replace it with classname.

Use class name instead.

In supporting Google Closure Compiler syntax.

For the record types to even reach type parser the DocParser needed
to be modified to parse the {...} type blocks by taking account the
need to balance the braces.

It completely puzzles me why Google Closure Compiler requires
varargs type name in function argument context to be wrapped inside
square braces, while in normal context no square brackets are needed.

But here we go...

And better structured tests.

Also now only allow optionality suffix "=" be used inside function type
arguments.

Needed for function type parameter types.

In supporting Google Closure compiler syntax.

- string
- number
- boolean
- null
- undefined

When "string" is used as type and String class exists, a link to
String class is created.  Otherwise just text "string" is shown.

In supporting Google Closure Compiler syntax.

To support Google Closure Compiler syntax for optional parameters.

    @param {Type=} name

This is detected at DocParser not in TypeParser like the rest of the
type definition syntax - all other way of defining optional parameters
are also implemented in DocParser, so it keeps things simpler to have it
all in there at one spot.

In supporting Google Closure Compiler syntax.

In supporting Google Closure Compiler syntax.

The syntax used by Google Closure Compiler.

Supported by Google Closure Compiler.

It was deprecated in 3.2.1 in December 2011.

Should be OK to remove now.

We can now have input files in any encoding as long as --encoding
option specifies it correctly.  When encoding differs from UTF-8,
we convert the text to UTF-8 internally and always output in UTF-8
also.

This option only works in Ruby 1.9.  Under 1.8 it has no effect.

In Ruby 1.9 reading files through builtin IO class attempted to
auto-detect the encoding which sometimes failed.

Created JsDuck::IO to be used instead of it, which forces all files
to be treated as UTF-8.  It also behaves well in Ruby 1.8 - just
doing nothing with the input and causing no errors.