Merge branch 'master' into comments

JsDuck

======

API documentation generator for Ext JS 4.

API documentation generator for Sencha JavaScript frameworks.

           ,~~.

          (  6 )-_,

    ~'`~'`~'`~'`~

JsDuck aims to be a better documentation generator for [Ext JS][] than

the old [ext-doc][] was. It is used by Sencha to generate the official

[Ext JS 4 documentation][ext4-docs].

the old [ext-doc][] was. It is used by Sencha to document [Ext JS

4][ext4-docs], [Sencha Touch][touch] and [several other][other-docs]

products.

The highlights of JSDuck are [Markdown][] support and keeping you DRY

by inferring a lot of information from code.  Read the [Guide][] for

[ext-doc]: http://ext-doc.org/

[Markdown]: http://daringfireball.net/projects/markdown/

[ext4-docs]: http://docs.sencha.com/ext-js/4-0/

[touch2-docs]: http://docs.sencha.com/touch/2-0/

[other-docs]: http://docs.sencha.com/ext-js/4-0/

[Guide]: https://github.com/senchalabs/jsduck/wiki/Guide

Getting it

----------

Standard rubygems install should do (use the `--pre` switch to get the

latest 3.0 version which this README documents, otherwise you will get

the stable but quite old [0.6][v0.6] version):

Standard rubygems install should do:

    $ [sudo] gem install --pre jsduck

    $ [sudo] gem install jsduck

If you encounter errors during gem installation, you may need to

install the header files for compiling extension modules for ruby 1.8.

which includes Ruby interpreter and all dependencies bundled in a

single .exe file.  Grab it from the [download page][].

[v0.6]: https://github.com/senchalabs/jsduck/tree/v0.6

[download page]: https://github.com/senchalabs/jsduck/downloads

Usage

To generate docs for Ext JS 4 add path to the corresponding src/ dir:

    $ jsduck extjs-4.0.2a/src \

    $ jsduck ext-4.0.7/src \

             --builtin-classes \

             --images extjs-4.0.2a/docs/doc-resources \

             --images ext-4.0.7/docs/images \

             --output your/docs

Running JSDuck with the current ext-4.0.2a release is expected to

generate a lot of warnings.  Because of the bugs in doc-comments a

global class will also get created.  You can disable this by adding

`--ignore-global` switch.  If you are bothered by the excessive amount

of warnings, use the `--no-warnings` switch.  For full list of command

line options type `jsduck --help=full`.

The `--images` option specifies a path for images included with

`{@img}` tags inside the source code.

To generate docs for your own project, simply name additional input

directories:

The latest ext-4.0.6 release will produce only few warnings, so use

that if you can get it.

    $ jsduck ext-4.0.7/src project1/js project2/js ...

Note that the resulting documentation will only contain the API

documentation.  Guides, videos and examples will not be present.

These can be added using more command line options, but for now those

aren't well documented as the ext-4.0.2a release doesn't contain the

source files for these.

To generate docs for your own project, simply add as many other input

directories as needed:

    $ jsduck --builtin-classes ext-4.0.2a/src project1/js project2/js --output your/docs

Of course you don't have to include the whole Ext JS into your

documentation, but if your project is built on top of it, it makes

sense to do so - otherwise you won't be able to see which methods your

classes inherit from Ext JS classes.

To create guides, videos and other sections, read about the

[Advanced Usage][adv] in wiki.

These can be added using more command line options as explained in the

[Advanced Usage][adv] section of wiki.

Running JSDuck against older Ext JS than 4.0.7 is expected to generate

a lot of warnings.  Similarly your own .js files will probably

generate warnings too.  Sorry for that, JSDuck just wants to be

helpful.  If you are overwhelmed by the warnings, you can disable them

using `--no-warnings` switch.  Another thing that often happens is

that JSDuck is unable to determine into which class a member belongs

and will place all such items into a global class - you can disable

this using the `--ignore-global` switch.  For full list of command

line options type `jsduck --help=full`.

[adv]: https://github.com/senchalabs/jsduck/wiki/Advanced-Usage

[Thomas Aylott](https://github.com/subtleGradient),

[johnnywengluu](https://github.com/johnnywengluu),

[gevik](https://github.com/gevik),

[ligaard](https://github.com/ligaard), and many-many others who

[ligaard](https://github.com/ligaard),

[Bill Hubbard](http://www.sencha.com/forum/member.php?272458-BillHubbard),

[Ed Spencer](https://github.com/edspencer),

[atian25](https://github.com/atian25) and many-many others who

reported bugs, submitted patches, and provided a lot of useful input.

Gem::Specification.new do |s|

  s.required_rubygems_version = ">= 1.3.7"

  s.required_rubygems_version = ">= 1.3.5"

  s.name = 'jsduck'

  s.version = '3.0.pre3'

  s.date = '2011-10-17'

  s.version = '3.0.1'

  s.date = '2011-10-22'

  s.summary = "Simple JavaScript Duckumentation generator"

  s.description = "Documentation generator for Sencha JS frameworks"

  s.homepage = "https://github.com/senchalabs/jsduck"

      @warnings = true

      @verbose = false

      @version = "3.0.pre3"

      @version = "3.0.1"

      # Customizing output

      @title = "Sencha Docs - Ext JS"

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

    <title>Sencha Examples</title>

    <script type="text/javascript" src="touch/sencha-touch-all.js"></script>

    <link rel="stylesheet" type="text/css" href="touch/resources/css/sencha-touch.css">

    <style id="iframe-css" type="text/css"></style>

    <style type="text/css" media="screen">

        html {

            overflow: hidden

        }

        .home {

            text-align: center;

        }

        .home img {

            width: 64%;

        }

        .home h1 {

            font-weight: bold;

            font-size: 1.2em;

        }

        .home p {

            color: #666;

            font-size: 0.8em;

            line-height: 1.5em;

            margin: 10px 20px 12px 20px;

        }

        .home h2 {

            color: #999;

            font-size: 0.7em;

        }

		.twitterView .x-dataview-item {

			padding: 10px;

			min-height: 50px;

		}

		.twitterView .x-dataview-item img {

			float: left;

			display: block;

			margin-top: 36px;

		}

		.twitterView .x-dataview-item h2 {

			font-weight: bold;

			color: #333;

			margin: 0px 0px 10px 60px;

		}

		.twitterView .x-dataview-item p {

			color: #666;

			margin-left: 60px;

			font-size: 0.8em;

		}

    </style>

    <script type="text/javascript" src="extjs/ext-all.js"></script>

    <link rel="stylesheet" type="text/css" href="extjs/resources/css/ext-all.css">

    <script type="text/javascript">

        function loadInlineExample(code, options) {

            try {

                document.body.innerHTML = '';

                if (!options.raw) {

                    code = "Ext.setup({onReady: function(){" + code + "}});";

                }

                if (options.tablet) {

                    // Scale example down to 70% size. Default font-size is 114%

                    Ext.get('iframe-css').update("body {font-size: 79.8% !important}");

                }

                eval(code);

            } catch (e) {

                document.body.innerHTML = e;