<?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>Thu, 17 May 2012 03:33:55 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Mike Naberezny's Blog: Symfony Templates and Ruby's ERb]]></title>
      <guid>http://www.phpdeveloper.org/news/4865</guid>
      <link>http://www.phpdeveloper.org/news/4865</link>
      <description><![CDATA[In his <a href="http://www.mikenaberezny.com/archives/40">latest blog entry</a>, <i>Mike Naberezny</i> takes a look at the <a href="http://symfony-project.com/">Symfony framework</a> and shares some of his opinions on it.
<p>
<quote>
<i>
One thing that I think Symfony gets right is that it appears to use partitioned PHP code for its templates, in the spirit of <a href="http://www.paul-m-jones.com/">Paul</a>'s <a href="http://www.phpsavant.com/">Savant</a> system.
<p>
I noticed in the Symfony demo that there is no separation of scope between variables passed to the template from the controller and local variables in the template. I'd like to see them scoped properly ("$this->products") but I can certainly understand why they did it this way. Using "$this->" in the template everywhere quickly gets messy.
</i>
</quote>
<p>
He <a href="http://www.mikenaberezny.com/archives/40">mentions</a> a few other items he saw as well, including a way to correct the above mentioned problem (two ways - one more single-instance, the other more global).]]></description>
      <pubDate>Wed, 20 Feb 2008 07:12:36 -0600</pubDate>
    </item>
  </channel>
</rss>

