<?xml version="1.0" encoding="UTF-8"?>
<!-- Reviewed: no -->
<sect2 id="zend.dojo.view.dojo">
    <title>dojo() View Helper</title>

    <para>
        The <methodname>dojo()</methodname> view helper is intended to simplify setting up
        the Dojo environment, including the following responsibilities:
    </para>

    <itemizedlist>
        <listitem><para>Specifying either a CDN or a local path to a Dojo
                install.</para></listitem>
        <listitem><para>Specifying paths to custom Dojo modules.</para></listitem>
        <listitem><para>Specifying dojo.require statements.</para></listitem>
        <listitem><para>Specifying dijit stylesheet themes to use.</para></listitem>
        <listitem><para>Specifying dojo.addOnLoad() events.</para></listitem>
    </itemizedlist>

    <para>
        The <methodname>dojo()</methodname> view helper implementation is an example of a
        placeholder implementation. The data set in it persists between view
        objects and may be directly echoed from your layout script.
    </para>

    <example id="zend.dojo.view.dojo.usage">
        <title>dojo() View Helper Usage Example</title>

        <para>
            For this example, let's assume the developer will be using Dojo from
            a local path, will require several dijits, and will be
            utilizing the Tundra dijit theme.
        </para>

        <para>
            On many pages, the developer may not utilize Dojo at all. So, we
            will first focus on a view script where Dojo is needed and then on the
            layout script, where we will setup some of the Dojo environment and
            then render it.
        </para>

        <para>
            First, we need to tell our view object to use the Dojo view helper
            paths. This can be done in your bootstrap or an early-running
            plugin; simply grab your view object and execute the following:
        </para>

        <programlisting language="php"><![CDATA[
$view->addHelperPath('Zend/Dojo/View/Helper/', 'Zend_Dojo_View_Helper');
]]></programlisting>

        <para>
            Next, the view script. In this case, we're going to specify
            that we will be using a FilteringSelect -- which will consume a
            custom store based on QueryReadStore, which we'll call
            'PairedStore' and store in our 'custom' module.
        </para>

        <programlisting language="php"><![CDATA[
<?php // setup data store for FilteringSelect ?>
<div dojoType="custom.PairedStore" jsId="stateStore"
    url="/data/autocomplete/type/state/format/ajax"
    requestMethod="get"></div>

<?php // Input element: ?>
State: <input id="state" dojoType="dijit.form.FilteringSelect"
    store="stateStore" pageSize="5" />

<?php // setup required dojo elements:
$this->dojo()->enable()
             ->setDjConfigOption('parseOnLoad', true)
             ->registerModulePath('custom', '../custom/')
             ->requireModule('dijit.form.FilteringSelect')
             ->requireModule('custom.PairedStore'); ?>
]]></programlisting>

        <para>
            In our layout script, we'll then check to see if Dojo is enabled,
            and, if so, we'll do some more general configuration and assemble
            it:
        </para>

        <programlisting language="php"><![CDATA[
<?php echo $this->doctype() ?>
<html>
<head>
    <?php echo $this->headTitle() ?>
    <?php echo $this->headMeta() ?>
    <?php echo $this->headLink() ?>
    <?php echo $this->headStyle() ?>
<?php if ($this->dojo()->isEnabled()){
    $this->dojo()->setLocalPath('/js/dojo/dojo.js')
                 ->addStyleSheetModule('dijit.themes.tundra');
    echo $this->dojo();
   }
?>
    <?php echo $this->headScript() ?>
</head>
<body class="tundra">
    <?php echo $this->layout()->content ?>
    <?php echo $this->inlineScript() ?>
</body>
</html>
]]></programlisting>

        <para>
            At this point, you only need to ensure that your files are in the
            correct locations and that you've created the end point action for
            your FilteringSelect!
        </para>
    </example>

    <sect3 id="zend.dojo.view.dojo.declarative">
        <title>Programmatic and Declarative Usage of Dojo</title>

        <para>
            Dojo allows both <emphasis>declarative</emphasis> and
            <emphasis>programmatic</emphasis> usage of many of its features.
            <emphasis>Declarative</emphasis> usage uses standard HTML elements
            with non-standard attributes that are parsed when the page is
            loaded. While this is a powerful and simple syntax to utilize, for
            many developers this can cause issues with page validation.
        </para>

        <para>
            <emphasis>Programmatic</emphasis> usage allows the developer to
            decorate existing elements by pulling them by ID or <acronym>CSS</acronym> selectors
            and passing them to the appropriate object constructors in Dojo.
            Because no non-standard HTML attributes are used, pages continue to
            validate.
        </para>

        <para>
            In practice, both use cases allow for graceful degradation when
            javascript is disabled or the various Dojo script resources are
            unreachable. To promote standards and document validation,
            Zend Framework uses programmatic usage by default; the various view
            helpers will generate javascript and push it to the
            <methodname>dojo()</methodname> view helper for inclusion when rendered.
        </para>

        <para>
            Developers using this technique may also wish to explore the option
            of writing their own programmatic decoration of the page. One
            benefit would be the ability to specify handlers for dijit events.
        </para>

        <para>
            To allow this, as well as the ability to use declarative syntax,
            there are a number of static methods available to set this behavior
            globally.
        </para>

        <example id="zend.dojo.view.dojo.declarative.usage">
            <title>Specifying Declarative and Programmatic Dojo Usage</title>

            <para>
                To specify declarative usage, simply call the static
                <methodname>setUseDeclarative()</methodname> method:
            </para>

            <programlisting language="php"><![CDATA[
Zend_Dojo_View_Helper_Dojo::setUseDeclarative();
]]></programlisting>

            <para>
                If you decide instead to use programmatic usage, call the static
                <methodname>setUseProgrammatic()</methodname> method:
            </para>

            <programlisting language="php"><![CDATA[
Zend_Dojo_View_Helper_Dojo::setUseProgrammatic();
]]></programlisting>

            <para>
                Finally, if you want to create your own programmatic rules, you
                should specify programmatic usage, but pass in the value '-1';
                in this situation, no javascript for decorating any dijits used
                will be created.
            </para>

            <programlisting language="php"><![CDATA[
Zend_Dojo_View_Helper_Dojo::setUseProgrammatic(-1);
]]></programlisting>
        </example>
    </sect3>

    <sect3 id="zend.dojo.view.dojo.themes">
        <title>Themes</title>

        <para>
            Dojo allows the creation of themes for its dijits (widgets). You may
            select one by passing in a module path:
        </para>

        <programlisting language="php"><![CDATA[
$view->dojo()->addStylesheetModule('dijit.themes.tundra');
]]></programlisting>

        <para>
            The module path is discovered by using the character '.' as a
            directory separator and using the last value in the list as the name
            of the <acronym>CSS</acronym> file in that theme directory to use; in the example
            above, Dojo will look for the theme in
            'dijit/themes/tundra/tundra.css'.
        </para>

        <para>
            When using a theme, it is important to remember to pass the theme
            class to, at the least, a container surrounding any dijits you are
            using; the most common use case is to pass it in the body:
        </para>

        <programlisting language="html"><![CDATA[
<body class="tundra">
]]></programlisting>
    </sect3>

    <sect3 id="zend.dojo.view.dojo.layers">
        <title>Using Layers (Custom Builds)</title>

        <para>
            By default, when you use a dojo.require statement, dojo will make a
            request back to the server to grab the appropriate javascript file.
            If you have many dijits in place, this results in many requests to
            the server -- which is not optimal.
        </para>

        <para>
            Dojo's answer to this is to provide the ability to create
            <emphasis>custom builds</emphasis>. Builds do several things:
        </para>

        <itemizedlist>
            <listitem><para>
                Groups required files into <emphasis>layers</emphasis>; a layer
                lumps all required files into a single JS file. (Hence the name
                of this section.)
            </para></listitem>

            <listitem><para>
                "Interns" non-javascript files used by dijits (typically,
                template files). These are also grouped in the same JS file as
                the layer.
            </para></listitem>

            <listitem><para>
                Passes the file through ShrinkSafe, which strips whitespace and
                comments, as well as shortens variable names.
            </para></listitem>
        </itemizedlist>

        <para>
            Some files can not be layered, but the build process will create a
            special release directory with the layer file and all other files.
            This allows you to have a slimmed-down distribution customized for
            your site or application needs.
        </para>

        <para>
            To use a layer, the <methodname>dojo()</methodname> view helper has a
            <methodname>addLayer()</methodname> method for adding paths to required layers:
        </para>

        <programlisting language="html"><![CDATA[
$view->dojo()->addLayer('/js/foo/foo.js');
]]></programlisting>

        <para>
            For more information on creating custom builds, please <ulink
                url="http://dojotoolkit.org/book/dojo-book-0-9/part-4-meta-dojo/package-system-and-custom-builds">refer
                to the Dojo build documentation</ulink>.
        </para>
    </sect3>

    <sect3 id="zend.dojo.view.dojo.methods">
        <title>Methods Available</title>

        <para>
            The <methodname>dojo()</methodname> view helper always returns an instance of
            the dojo placeholder container. That container object has the
            following methods available:
        </para>

        <itemizedlist>
            <listitem><para><methodname>setView(Zend_View_Interface $view)</methodname>: set
                    a view instance in the container.</para></listitem>
            <listitem><para><methodname>enable()</methodname>: explicitly enable Dojo
                    integration.</para></listitem>
            <listitem><para><methodname>disable()</methodname>: disable Dojo
                    integration.</para></listitem>
            <listitem><para><methodname>isEnabled()</methodname>: determine whether or not
                    Dojo integration is enabled.</para></listitem>
            <listitem><para><methodname>requireModule($module)</methodname>: setup a
                    <code>dojo.require</code> statement.</para></listitem>
            <listitem><para><methodname>getModules()</methodname>: determine what modules
                    have been required.</para></listitem>
            <listitem><para><methodname>registerModulePath($module, $path)</methodname>:
                    register a custom Dojo module path.</para></listitem>
            <listitem><para><methodname>getModulePaths()</methodname>: get list of
                    registered module paths.</para></listitem>
            <listitem><para><methodname>addLayer($path)</methodname>: add a layer (custom
                    build) path to use.</para></listitem>
            <listitem><para><methodname>getLayers()</methodname>: get a list of all
                    registered layer paths (custom builds).</para></listitem>
            <listitem><para><methodname>removeLayer($path)</methodname>: remove the layer
                    that matches <varname>$path</varname> from the list of registered
                    layers (custom builds).</para></listitem>
            <listitem>
                <para>
                    <methodname>setCdnBase($url)</methodname>: set the base <acronym>URL</acronym>
                    for a CDN; typically, one of the <constant>Zend_Dojo::CDN_BASE_AOL</constant> or
                    <constant>Zend_Dojo::CDN_BASE_GOOGLE</constant>, but it only needs
                    to be the <acronym>URL</acronym> string prior to the version number.
                </para>
            </listitem>
            <listitem><para><methodname>getCdnBase()</methodname>: retrieve the base CDN url
                    to utilize.</para></listitem>
            <listitem><para><methodname>setCdnVersion($version = null)</methodname>: set
                    which version of Dojo to utilize from the CDN.</para></listitem>
            <listitem><para><methodname>getCdnVersion()</methodname>: retrieve what
                    version of Dojo from the CDN will be used.</para></listitem>
            <listitem><para><methodname>setCdnDojoPath($path)</methodname>: set the relative
                    path to the dojo.js or dojo.xd.js file on a CDN; typically,
                    one of the <constant>Zend_Dojo::CDN_DOJO_PATH_AOL</constant> or
                    <constant>Zend_Dojo::CDN_DOJO_PATH_GOOGLE</constant>, but it only
                    needs to be the path string following the version
                    number.</para></listitem>
            <listitem><para><methodname>getCdnDojoPath()</methodname>: retrieve the last
                    path segment of the CDN url pointing to the dojo.js
                    file.</para></listitem>
            <listitem><para><methodname>useCdn()</methodname>: tell the container to
                    utilize the CDN; implicitly enables integration.</para></listitem>
            <listitem><para><methodname>setLocalPath($path)</methodname>: tell the container
                    the path to a local Dojo install (should be a path relative
                    to the server, and contain the dojo.js file itself);
                    implicitly enables integration.</para></listitem>
            <listitem><para><methodname>getLocalPath()</methodname>: determine what local
                    path to Dojo is being used.</para></listitem>
            <listitem><para><methodname>useLocalPath()</methodname>: is the integration
                    utilizing a Dojo local path?</para></listitem>
            <listitem><para><methodname>setDjConfig(array $config)</methodname>: set
                    dojo/dijit configuration values (expects assoc
                    array).</para></listitem>
            <listitem><para><methodname>setDjConfigOption($option, $value)</methodname>: set
                    a single dojo/dijit configuration value.</para></listitem>
            <listitem><para><methodname>getDjConfig()</methodname>: get all dojo/dijit
                    configuration values.</para></listitem>
            <listitem><para><code>getDjConfigOption($option, $default =
                    null)</code>: get a single dojo/dijit configuration
                    value.</para></listitem>
            <listitem><para><methodname>addStylesheetModule($module)</methodname>: add a
                    stylesheet based on a module theme.</para></listitem>
            <listitem><para><methodname>getStylesheetModules()</methodname>: get stylesheets
                    registered as module themes.</para></listitem>
            <listitem><para><methodname>addStylesheet($path)</methodname>: add a local
                    stylesheet for use with Dojo.</para></listitem>
            <listitem><para><methodname>getStylesheets()</methodname>: get local Dojo
                    stylesheets.</para></listitem>
            <listitem><para><methodname>addOnLoad($spec, $function = null)</methodname>: add
                    a lambda for dojo.onLoad to call. If one argument is passed,
                    it is assumed to be either a function name or a javascript
                    closure. If two arguments are passed, the first is assumed
                    to be the name of an object instance variable and the second
                    either a method name in that object or a closure to utilize
                    with that object.</para></listitem>
            <listitem><para><methodname>prependOnLoad($spec, $function = null)</methodname>:
                    exactly like <methodname>addOnLoad()</methodname>, excepts prepends to
                    beginning of onLoad stack.</para></listitem>
            <listitem><para><methodname>getOnLoadActions()</methodname>: retrieve all
                    dojo.onLoad actions registered with the container. This will
                    be an array of arrays.</para></listitem>
            <listitem><para><methodname>onLoadCaptureStart($obj = null)</methodname>:
                    capture data to be used as a lambda for dojo.onLoad(). If
                    $obj is provided, the captured JS code will be considered a
                    closure to use with that Javascript object.</para></listitem>
            <listitem><para><methodname>onLoadCaptureEnd($obj = null)</methodname>: finish
                    capturing data for use with dojo.onLoad().</para></listitem>
            <listitem><para><methodname>javascriptCaptureStart()</methodname>:
                    capture arbitrary javascript to be included with Dojo JS
                    (onLoad, require, etc. statements).</para></listitem>
            <listitem><para><methodname>javascriptCaptureEnd()</methodname>: finish
                    capturing javascript.</para></listitem>
            <listitem><para><methodname>__toString()</methodname>: cast the container to a
                    string; renders all HTML style and script elements.</para></listitem>
        </itemizedlist>
    </sect3>
</sect2>
<!--
vim:se ts=4 sw=4 et:
-->
