Removed from anything that is wrapped by gem when installed by gem.
Fixes #338.

To allow for simpler way to supply the old version warning message.

Just a useful shorthand during development.

Provide just the basic info and reference the wiki guide for details.

The #open and #close methods of HtmlStack now take StringScanner
as input and work at a higher level.

This is currently the latest version.

For some reason the docs app had an hard-coded minimum with.
This severely impacted the usability on iPad where the browser window
width was smaller than our min-width, resulting in text going off the
screen and there being no way to get to it.

For some reason I had always thought \Z is the end of string in Ruby,
but it turns out \z is actually the end of string while \Z will match
right before a newline at the end of string if there happens to be one.

This little difference caused quite an unexpected behavior in one corner
case where the code example is on just a line before the @tag.

Splitting up the humongous Link class into more managable pieces.

The DocFormatter constructor now takes two parameters - relations and
options, instead of passing the relations in separately.  It then
instantiates LinkRenderer and passes it to Link and AutoLink
constructors.

The LinkRenderer is still too heavily coupled to Link and AutoLink,
as these call all the methods of LinkRenderer, but the situation is
much better overall.

Previously all auto-linked classnames had to begin with uppercase char,
but that's not really needed as we only replace namespaced classnames
anyway.

Just an ordinary refactoring.

Both the ImagesDir and ImagesDirSet now have #report_unused method.
No more is the unused images reporting part of #copy method.

Also take care to ignore the icon.png and icon-lg.png files inside
guides - these don't have to be reference by @img tag, but are
used automatically.

Include the Dimensions gem to retrieve image width/height meta-data.

Additional %w an %h placeholders to --img-tpl template.

Achieving this required extensive refactoring of how the images get
processed.  Previously the existance of images was looked up after
all the @img tag had been replaced.  Now the check for existance is
part of expanding the @img tag, so the check happens also for images
in guides, for which the check didn't occour previously as there is
no images copy step in there.

The old Images class has been replaced with ImageDir and ImageDirSet.

Added additional styles for the welcome page so that when it's
rendered from Markdown, the default result will look OK.

That's much better than the previous flickering where before performing
the search the dropdown was shown and after getting no results it was
hidden again.

Better to just show a message "Nothing found" - this will also make
clear to the user that the search found no results and didn't just fail
for whatever reason.

The Class#find_members(:local=>true) previously also returned
the hidden members.  This resulted from the fact that internally
it was using #global_by_id and #local_by_id indexes from MembersIndex
class.  As these maps are also used internally inside MembersIndex
I'm now exposing #all_global and #all_local methods which return
the arrays instead of hashes and both without any hidden members.

In commented out form, to be used when needed.

The "|" is used as table cell separator and inside a table cell
needs to be escaped with HTML entity.

Otherwise the documentation inheriting process will run into infinite
loop.

For example the following code cause a problem:

    /**
     * @class
     * @extends B
     */
    A = {};

    /**
     * @class
     * @extends A
     */
    B = {c: 'd'};

That's fixed now.

No more does using this option restrict viewing of inline examples
to WebKit based browsers.  This check is now moved over to
eg-iframe.html in Sencha Touch codebase.

This fixes the issue of return value docs being completely missing
in case @return wasn't followed by {TypeDef}.

Instead of using hardcoded image with text "Sencha Docs".

Don't direct people right away to JSDuck issue tracker - most likely
it's just a fault of a broken link and it's the authors of the
documentation who should fix it.

A silly mistake.