When @multiline is set to true in MetaTag implementation, multiple
lines after the tag up to next @tag will be included to meta-tag
contents.

Each meta-tag is now implemented as a class.  The --meta-tags option
specifies a path to Ruby file that contains the implementations.

By default the sencha_tags.rb file is included which implements
@author and @docauthor as hidden tags.

This is a switch away from ext-doc style tree-logic where the tree
could look like this:

    - Foo
      - Bar
      - Bar.Baz
      - Bar.Zap

Now the tree always looks like this:

    - Foo
      - Bar
        - Baz
        - Zap

This change is mostly in response to request of a user working with
a system where most package names were also classes.  With previous
PackageLogic implementation he ended up with a pretty flat tree.

The support has been implemented for a while, but nobody has ever
really used the functionality. Time to remove it. Along with it
goes the --inline-examples option.

Touch 2 sources seem to contain no {@img} tags.

Using this will switch on the Touch-style examples page where
examples are shown inside iPhone/iPad images.

For now the option will also decide from where the icons for examples
are loaded: touch/examles or extjs/examples/shared/screens

There are now two implementations of example container:

- Container
- TouchContainer

Changing terminology: using "tablet" and "phone" instead of "iPad" and
"iPhone".

Changing default device to "phone".  See also the updated examples.json
in touch-2.0.0 where I added device info to each example.

Move all the changeDevice and changeOrientation logic inside the view.
The state of buttons is now also handled inside the view - the buttons
now actually behave as expected.

Also the example title gets now updated and the XTemplate is created
inside initComponent.

If it's not used, then it's better if the code for it doesn't exist at
all, or it will just get out of sync, which has already happened.

Removing empty lines, trailing commas, etc.

Copying of touch build was done inside copy_touch2_images, which
wasn't really the correct place.  Also, all the copy_*_images
methods were removed, so I created a separate copy_touch_build
method.

Now all images can be marked up the same way - no need for special
syntax in guides.

Using this, JSDuck will automatically copy over images referenced
by {@img} tag.  No more need for extra copy task after running JSDuck.

The categories JSON file must now just contain an array, just like
the JSON files for videos, guides and examples do.

Simplicity FTW!

Filename always at the beginning, followed by line number and message.

JS files not needed if --welcome, --guides, --videos or --examples
options provided.

Also hide the classes tab and page in this case.