<?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, 04 Jul 2008 16:56:40 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: The HYSOCAMTT templating approach]]></title>
      <guid>http://www.phpdeveloper.org/news/9707</guid>
      <link>http://www.phpdeveloper.org/news/9707</link>
      <description><![CDATA[<p>
In a new post to the Zend Developer Zone, <i>Brett Zamir</i> has <a href="http://devzone.zend.com/article/2814-The-HYSOCAMTT-templating-approach">posted a new tutorial</a> that talks about using the Smarty templating system to create what he calls the HYSOCAMTT templating approach ("Have-Your-Separation-Of-Concerns-And-Mix-Them-Too".
</p>
<blockquote>
This article aims to highlight a approach which allows one to separate everything from one's business logic to one's design logic, to XHTML from CSS, one's Javascript from the page structure, etc., while at the same time being able to be lazy and include, for example, CSS information within the same document (template) as one's XHTML
</blockquote>
<p>
The tutorial uses an extension for Smarty called <a href="http://sourceforge.net/projects/smartydocb">SmartyDocB</a> that makes the documentation side much easier. He works through the templating process and includes some of the code for the .tpl files to get you started.
</p>
<p>
He also includes some future goals for his idea, a mention of XSL templating, XQuery and the potential for templating across programming languages to make your site even more flexible.
</p>]]></description>
      <pubDate>Wed, 27 Feb 2008 07:56:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[phpRiot.com: Application logic versus template logic]]></title>
      <guid>http://www.phpdeveloper.org/news/5286</guid>
      <link>http://www.phpdeveloper.org/news/5286</link>
      <description><![CDATA[<p>
phpRiot.com has posted <a href="http://www.phpriot.com/d/articles/php/templates/application-logic-vs-template-logic/index.html">this new tutorial</a> today that looks at a method to seperate out the application logic and the templates for your site. Their weapon of choice is the <a href="http://smarty.php.net/">Smarty Template Engine</a>.
</p>
<quote>
<i>
What this is basically saying is that anything relating to the final output should be determined in the template, while any data handling or processing should be done in your PHP files and classes. There's a little more to it than though, which we'll soon see.
</i>
</quote>
<p>
They <a href="http://www.phpriot.com/d/articles/php/templates/application-logic-vs-template-logic/index.html">introduce</a> the reader to what the two sides are (application and template logic) and an example of the "bad way" to do things - application logic in your presentation layer. To counter this, they give examples of proper structure with examples like checking strings, alternating background colors, showing a counter, and the inclusion of another template.
</p>
<p>
A few other suggestions are made as to the good and the bad of templating your site, including two cases showing both sides.
</p>]]></description>
      <pubDate>Tue, 02 May 2006 07:41:02 -0500</pubDate>
    </item>
  </channel>
</rss>
