<?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, 18 May 2013 07:30:20 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tony Bibbs' Blog: MVCnPHP (A Framework)]]></title>
      <guid>http://www.phpdeveloper.org/news/12134</guid>
      <link>http://www.phpdeveloper.org/news/12134</link>
      <description><![CDATA[<p>
<i>Tony Bibbs</i> has <a href="http://www.tonybibbs.com/article.php/MVCnPHP-Announcement">made a release</a> of an MVC framework that's been a few years of his development time in the making - <a href="http://www.apteno.net/AptitudeCMS/trac/wiki/MVCnPHPProject">MVCnPHP</a>.
</p>
<blockquote>
I will start this blog entry by saying I like <A href="http://framework.zend.com/">Zend Framework</a>. I really do. However, the part of ZF I don't use is the MVC implementation. No, it's not bad. Actually it's a good implementation that is the product of a lot of hard work by Zenders and non-Zenders alike. I use bits and pieces of ZF in my PHP projects and, admittedly, Zend's MVC implementation never made the cut.
</blockquote>
<p>
He decided a while back on his own implementation and has stuck with it over the years. He still uses the components of the Zend Framework but not the routing and model/view/controller setup of it all. Instead he's opted for his own <a href="http://www.apteno.net/AptitudeCMS/trac/wiki/MVCnPHPProject">MVCnPHP</a> methods for his own applications. You can check out these resource for more information: <a href="http://mvcnphp-demo.apteno.net/">a sample application</a>, <a href="http://www.apteno.net/AptitudeCMS/trac/wiki/MVCnPHPGuide">the user guide</a> and, of course, <a href="http://www.apteno.net/AptitudeCMS/trac/wiki/MVCnPHPInstallation">the framework's download page</a>.
</p>]]></description>
      <pubDate>Fri, 13 Mar 2009 12:50:46 -0500</pubDate>
    </item>
  </channel>
</rss>
