Now it only contains tasks directly related to JSDuck and two
helper tasks to generate touch and ext docs from SDK.

In addition to making the member itself visible, we also make its
containing section visible if needed.

Because we're using JsonP requests the browser simply doesn't give us
any information as of why the loading of <script> tag failed - it just
says: "error".

The hierarchy <pre> element happened to get the .notpretty class
added which resulted in different margins etc.  Now avoiding that.

Also fixed the color of normal text inside it.

The CSS is supplied from Touch SDK repository.

Consequently one cannot use the old sencha command any more.

That's no more needed in ExtJS 4.1.

Instead pick the build pointed to by template/extjs/

This way the EXT_BUILD var only affects which version of ExtJS will be
used for inline examples.

Guides and videos are now panels, so the comments need to be added to
the panel body element, not the top element.

Fix the issue of hover menu not getting hidden at all when the button is
hovered for the first time and then immediately mouse moves away.

Use initConfig() instead of Ext.apply().

Fixes Touch examples when Docs app is running under Ext 4.1.

Some divs were not closed.

This fixes layout issues when view Touch examples under ExtJS 4.1

The main styles were restricted to panel body, but guides and others
were containers, not panels, so the styles did not get applied.

Now guides, videos, comments are all panels.

Instead of injecting the button to the toolbar from outside, the toolbar
itself manages the button, providing methods to show and update it.

Also the toolbar now fires an event when the comment count button is
clicked - the comments controller just needs to handle that event, not
deal with binding the event to toolbar element after render.

Add a bit more top-bottom padding to the toolbar.

Move the styles from JavaScript to CSS and document.

Some previous <pre>-related style tweaks resulted in <pre> line height
being no more applied to the CodeMirror editor.  Now explicitly stored
the line-height style.

CodeMirror just defines the rule:

    .CodeMirror pre { ... }

This selector has quite low specificity, so it's easy to accidentally
override it.  And this indeed happened when the selector for normal pre
elements was changed from:

    .class-overview pre { ... }

to:

    .class-overview .x-panel-body pre { ... }

The result was that a <pre> inside CodeMirror editor received unwanted
rounded corners etc, rendering the editor pretty-much unusable.

Resolved this by only styling pre.prettyprint and pre.notpretty.
(The latter class is now added to all not-to-be-prettified pre-s, which
distinguishes them from pre-s used inside CodeMirror component.)

Use Ext.clone when passing #data config to store to avoid the
destructive behavior.

In addition to stack trace the name of the file causing the problem is
printed.

It took hours to track this down... and I'm out of ideas of why we need
to require this class over there.

First I'm constraining the styles of the main class-overview container
inside the body-area - otherwise the styles will also have unpredictable
effects on toolbar (especially the styles for tables as in 4.1 the
search field inside toolbar is wrapped in two tables).

Secondly the search field styles are applied differently as the DOM that
makes up the field has changed considerably.  At the moment this results
in the field looking a bit different in 4.1.  Needs more work...

Also added width to the trigger-field which otherwise would change its
width when trigger is shown/hidden.