<?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>Wed, 22 May 2013 19:15:01 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Davey Shafik's Blog: Detailed IDE Reviews: How do you want to do this?]]></title>
      <guid>http://www.phpdeveloper.org/news/12155</guid>
      <link>http://www.phpdeveloper.org/news/12155</link>
      <description><![CDATA[<p>
As a follow-up to <a href="http://www.phpdeveloper.org/news/12145">the IDE comparisons</a> he's done <i>Davey Shafik</i> has <a href="http://pixelated-dreams.com/archives/557-detailed-ide-reviews.html">asked the interested</a> for a little feedback on how they think he should move forward with the more detailed reviews of each tool.
</p>
<blockquote>
So, dear readers, I'm doing the IDE reviews for all of you guys and there's two ways I can proceed: I can take each of the requirements and do a single post per requirement with a writeup about it in detail for each of the 4 IDEs - then I was thinking for each new IDE I try, I can hit those same points. Or I can write up specifically on a single editor at a time, covering all of the requirements and I will also then review anything else about the editor etc.
</blockquote>
<p>
He's thinking of doing a comparison of the Eclipse-based IDEs in their own right, but wants to get feedback on what would be the most useful for other developers to learn from. Several <a href="http://pixelated-dreams.com/archives/557-detailed-ide-reviews.html#comments">comments</a> have already been made suggesting approaches to the topic, other editors that might be missing from the list and some support for the Eclipse comparison idea.
</p>]]></description>
      <pubDate>Tue, 17 Mar 2009 13:45:14 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPBuilder.com: PHP Form Validation System: An Object-Oriented Approach]]></title>
      <guid>http://www.phpdeveloper.org/news/10005</guid>
      <link>http://www.phpdeveloper.org/news/10005</link>
      <description><![CDATA[<p>
<i>Mike Weiner</i> has put together <a href="http://www.phpbuilder.com/columns/weiner20050831.php3">an article</a> for PHPBuilder.com that's posted today showing a bit more object-oriented solution to validating the user submitted data in your forms:
</p>
<blockquote>
Whether it is for database submission, emailing, or for some other purpose, forms represent the primary means of enabling a user to send data to an application. As a result, it is important to have control over the data collected by your forms, which will aid in the creation of streamlined, error-free applications.
</blockquote>
<p>
He lays out the validation method in a graphic going with a generic validation class that then calls the various validation methods (like phone or email) as needed. The "validation set" manages which validations are to be run on which form elements. Example code for each of the bits making up the structure and the implementation are provided.
</p>]]></description>
      <pubDate>Mon, 21 Apr 2008 08:49:24 -0500</pubDate>
    </item>
    <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>
  </channel>
</rss>
