The code relied on the order of events being fired.  It expected that
when clicking tab close button the "click" handler for close button
will be invoked before the "click" handler for the whole tab.  This
worked in the majority of browsers but not in IE8 where the events
fire in the opposite order.

Now checking the event target inside tab click handler to see if
close button was clicked instead of relying on the close button handler
to set a flag.

This also fixes the issue of tabs sometimes not activating when clicked
in IE8.  Was caused by justClosed flag being set but not unset.

The return value of Array.indexOf was bogusly compared to false,
but #indexOf returns -1 not false on failure.

The official extjs-4.0.7 release has a bug in cors support where
it mistakenly checks for Ext.isIe instead of Ext.isIE.

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.