| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364 |
- <?xml version="1.0" encoding="UTF-8"?>
- <!-- Reviewed: no -->
- <sect1 id="zend.layout.introduction">
- <title>Introduction</title>
- <para>
- <classname>Zend_Layout</classname> implements a classic Two Step View pattern,
- allowing developers to wrap application content within another view,
- usually representing the site template. Such templates are often termed
- <emphasis>layouts</emphasis> by other projects, and Zend Framework has
- adopted this term for consistency.
- </para>
- <para>
- The main goals of <classname>Zend_Layout</classname> are as follows:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Automate selection and rendering of layouts when used with the
- Zend Framework <acronym>MVC</acronym> components.
- </para>
- </listitem>
- <listitem>
- <para>
- Provide separate scope for layout related variables and content.
- </para>
- </listitem>
- <listitem>
- <para>
- Allow configuration, including layout name, layout script
- resolution (inflection), and layout script path.
- </para>
- </listitem>
- <listitem>
- <para>
- Allow disabling layouts, changing layout scripts, and other
- states; allow these actions from within action controllers and
- view scripts.
- </para>
- </listitem>
- <listitem>
- <para>
- Follow same script resolution rules (inflection) as the <link
- linkend="zend.controller.actionhelpers.viewrenderer">ViewRenderer</link>,
- but allow them to also use different rules.
- </para>
- </listitem>
- <listitem>
- <para>
- Allow usage without Zend Framework <acronym>MVC</acronym> components.
- </para>
- </listitem>
- </itemizedlist>
- </sect1>
- <!--
- vim:se ts=4 sw=4 et:
- -->
|