The leaf property happened to have three possible values: true, false, undefined.
But it was assumed there's only two. Eliminated the undefined case.

For now I'm just turning it on for Touch 2.  But I'm thinking of making
it the default overall.

The device widths are all calculated now in one place.

50% size was right off - this way tablet examples would be smaller than phone
examples, plus the text became too small to read.

75% was also tried, but it seemed just a little bit too big, so I went
with 70%.

Also removed the duplicted iPad image files.

All words added after @example tag are converted into CSS classes.
The classes are detected in frontend and appropriate styling is applied.

The default is: phone landscape.

This greatly simplifies the Inline component, delegating the actual
preview showing and code editing to other classes.  More over the
InlineExamples controller no more deals with the iframe and many
other details directly.

Removed CSS-loading from both iframe files - for now it's not used.
Also removed error alert - writing the error message to document.body
should be enough, plus it's less obtrusive.

Inside touchIframe.html wrapping the code inside Ext.setup().
For start it will make most examples work.

That's currently a sort-of solution because the example itself in the
iframe is not scaled down at all.

Otherwise Touch will complain that Ext.setup has already been called.

- There are now two iframe files: extIframe.html and touchIframe.html.
- Touch iframe is wrapped inside div which renders iPhone border.
- The height of touch examples is fixed so that the phone image would
  fit.

When @cfg has both @accessor and @evented then an event is also
created in addition to get/set methods.

Also add empty meta-tags for the global class.

Instead link to the class itself.

Instead of :filename and :linenr properties being tied to class hash
itself, they are now inside :files property, which holds an array of
hashes which contain :filename and :linenr.

List of files is shown in the hierarchy sidebar. Especially useful for
classes like Ext.Element which are made up from many-many files.

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.