<?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>Sat, 25 May 2013 13:43:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lee Davis' Blog: FormFactory - Driving Doctrine 1.2 / 2.x Mappings into Zend_Form objects]]></title>
      <guid>http://www.phpdeveloper.org/news/17758</guid>
      <link>http://www.phpdeveloper.org/news/17758</link>
      <description><![CDATA[<p>
<i>Lee Davis</i> has <a href="http://www.duckheads.co.uk/drive-forms-from-doctrine-entities/">a recent post</a> to his blog showing how you can combine the Zend_Form component of the Zend Framework with Doctrine to help directly "drive" your forms.
</p>
<blockquote>
On a few of my previous projects I found myself creating more form classes than I'd like. And after the 30th one I figured there had to be a better way. I quickly realised that most of the elements within these forms shared similarities to the data type I would use on my database definitions. As I was using Doctrine at the time I figured I could not only drive my database from my mapping definitions, but my forms too.
</blockquote>
<p>
He shows how <a href="https://github.com/leedavis81/FormFactory>his library</a> (github) can be used to create a simple mapping between the form fields and the Doctrine entities, building from settings in an ini file. It also allows you to fall back to the normal Zend_Form configuration directives if you need something more custom. The <a href="http://www.duckheads.co.uk/drive-forms-from-doctrine-entities/">post</a> gets into more detail about using the project (configuring caching, other config options).
</p>
<p>
The project can be found <a href="https://github.com/leedavis81/FormFactory">here on github</a>.
</p>]]></description>
      <pubDate>Fri, 30 Mar 2012 10:43:57 -0500</pubDate>
    </item>
  </channel>
</rss>
