<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 01:40:19 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Weier O'Phinney's Blog: Rendering Zend_Form decorators individually]]></title>
      <guid>http://www.phpdeveloper.org/news/12319</guid>
      <link>http://www.phpdeveloper.org/news/12319</link>
      <description><![CDATA[<p>
<i>Matthew Weier O'Phinney</i> has <a href="http://weierophinney.net/matthew/archives/215-Rendering-Zend_Form-decorators-individually.html">another post</a> in his look at the decorator pattern in Zend Framework applications. This time he takes a step back and shows how to execute them individually.
</p>
<blockquote>
In the <a href="http://weierophinney.net/matthew/archives/213-From-the-inside-out-How-to-layer-decorators.html">previous installment</a> of this series on Zend_Form decorators, I looked at how you can combine decorators to create complex output. In that write-up, I noted that while you have a ton of flexibility with this approach, it also adds some complexity and overhead. In this article, I will show you how to render decorators individually in order to create custom markup for your form and/or individual elements.
</blockquote>
<p>
So, instead of registering them with the Zend_Form element, he shows how you can pull out the one decorator (with a getDecorator call) and render it separately. It can be simplified even more with the renderSimpleInput method called on the decorator object. He gives a use case example in defining a form that needs more exact control over the layout.
</p>]]></description>
      <pubDate>Fri, 10 Apr 2009 10:23:44 -0500</pubDate>
    </item>
  </channel>
</rss>
