<?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, 09 Jan 2009 22:36:26 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SitePoint PHP Blog: DOM vs. Template]]></title>
      <guid>http://www.phpdeveloper.org/news/11087</guid>
      <link>http://www.phpdeveloper.org/news/11087</link>
      <description><![CDATA[<p>
In <a href="http://www.pheedo.com/click.phdo?i=d87d9a59b65950a2cb059df2fc62a756">this new post</a> to the SitePoint PHP Blog there's a look at using a <a href="http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/">small templating engine</a> recently released by <i>Fredrik Holmstrom</i> that takes a different tack on working with template files - it parses them into a DOM structure.
</p>
<blockquote>
The main difference to traditional template engines (Such as <a href="http://www.smarty.net/">Smarty</a>), is that the template it self doesn't have any imperatives within. In fact, the template doesn't even have to be written to the template engine, to be used - Any markup can be used as a source.
</blockquote>
<p>
The templating system uses Domlings, bits of HTML to match against and replace with the bound information. A few examples are included - a simple binding, how to switch out a block of HTML, pushing it back in and looping over a block of information to do some search and replace.
</p>]]></description>
      <pubDate>Thu, 25 Sep 2008 11:18:25 -0500</pubDate>
    </item>
  </channel>
</rss>
