Only adding the clsName property for class nodes.

Removed .htaccess file, class URL-s are now in form:

    apidocs/#/api/Ext.Ajax

To make refreshing of a page work, added .htaccess file that
directs all api-URL-s to index.html.

Currently using URL in form: some-path/api:Ext.ClassName
I would like to use: some-path/api/Ext.ClassName

But I didn't figure out how to make them work, especially so that
it could be used from a local filesystem.  When the basedir of
the app changes, you can't use relative URL-s any more.

Before we had: "cfgs", "properties", "methods", ...
Now we have: "cfg", "property", "method", ...

Although naming array of events to just "event" looks at first
glance somewhat wrong, it makes looping over all the members
much-much easier.

Showing correct member names in member menus.

Replaced uses of Array.forEach with Ext.Array.forEach and
Ext.Array.map.

Divided the complex menu building logic into methods.

JSDuck now export JSON even in normal mode (without --json option).

When class name clicked in tree, the JSON is loaded and class
documentation displayd.  Currently we only show doc-comment of
the class.

Also turned off use of history.pushState - bringing it back in the
future.

Not needed, because we don't want to follow links directly,
but instead load JSON and generate the page.

- singleClickExpand
- cls

Because JSDuck creates the whole tree structure no complex conversion
is needed on JavaScript side - we just pass the JSDuck output to
treepanel root.

Renamed CSS classes in JSDuck generated tree data.

Brought over a lot of code from the docs app.
Then refactored the JavaScript heavily:

- Replaced tabs with spaces.
- Removed commented-out code.
- Moved global functions to functions.js
- Moved initialization to init.js

This defines the location of ExtJS directory.
It will be copied or symlinked to <output-dir>/extjs

This will allow us for now to skip adding the whole Ext4
to our small jsduck repo.

Useful when developing template files, to avoid running JSDuck every
time you make a change to JavaScript file.

Using this, suppresses the creation of global class and also
suppresses the error messages related to that.

Previously only the first "." got replaced in classname.

Before: Ext-panel.Panel-cfg-baseCls
After:  Ext-panel-Panel-cfg-baseCls

Previously the ID-part of members table rows was also cached,
resulting in ID containing the name of the class that happened to
be the first for which the row was generated.

That will contain list of mixins from the class and all its parent
classes.

Previously --img and --link only applied to export, but now they
can also be used to override the links/images in the normal output
of JSDuck.  Currently it's most useful for dealing with {@img} tags
in ExtJS 4.

Instead of linking to line numbers, documentable items in source files
are now nicely marked up, and are linked by name.  This should prevent
links to source from becoming outdated too quickly.

before: Ext.html#line-86
after:  Ext.html#Ext-method-apply

All the output is now done after parsing etc has finished.

All parsing and merging now happens inside that class.
Consequently the Agggregator is now a lot simpler, as
it takes for input just instance of SourceFile.

SourceFile instances contain all the input: filename, source, and
parsed doc-objects.

The output of HTML source files now happens after all the
parsing and aggregating, similarly to all other output.
For now the links to source code are still line-nr based,
but this will now be easy to change.

These allow to define templates to use in export for replacing
{@link} and {@img} tags.

Adjusting the markup of links and images is now much more flexible.
This will be most useful for customizing the markup in exports.

The tests also got simpler, as we can test agains simpler markup now.

The name is now in plural (although the singular @tag works too,
but inside JSDuck the name is now "alternateClassNames" and is also
exported with that name).

Overall it behaves like @mixins tag, which too can contain multiple
items.

Correctly implemented merging of mixins and alternateClassNames when
merging class definitions.

Alternate classnames are also shown in JSDuck generated docs.

When @mixins tag present, it will override all the implied mixins
possibly detected from code.  One can either use just one @mixins:

    @mixins Foo Bar Baz

Or several:

    @mixins Foo
    @mixins Bar
    @mixins Baz

The result will be the same.

So that the e-mail address after author name will also be shown.

Hard to get it correct when there are:

- Ext.extend(...
- Ext.define("MyClass", {extend: "Parent", ...

But in doc-comment you had to previously write "@extends".
Now it's similar to @returns, which can also be @return.

No matter if alternateClassName is missing, is a string or an array,
the result of parsing will always be an array - even if just one
item or empty.

Simplified the parsing - using array_of_strings method to do most
of the work.

Doing a proper parsing now, so automatic link-creation won't be
done inside {@link} and {@img}.

Simple-minded implementation with regex search-replace.