<?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>Sun, 11 May 2008 19:47:58 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Alan Knowles' Blog: Licence to release PHP code?]]></title>
      <guid>http://www.phpdeveloper.org/news/9878</guid>
      <link>http://www.phpdeveloper.org/news/9878</link>
      <description><![CDATA[<p>
A little while back, <i>Alan Knowles</i> <a href="http://www.akbkhome.com/blog.php/View/159/Licence_to_release_PHP_code.html">wondered something</a> that I'm sure has crosses the mind of every PHP developer out there, especially when they came across a particularly bad chunk of code - some people should need to apply for a license before releasing their PHP code out into the wild.
</p> 
<blockquote>
Unlike most of the reviews you get, I was specifically looking at code quality [of the CMSs]. not fuzzy does it look nice!
</blockquote>
<p>
He looks at a whole list of them including: Tanslucis, Siteman, Pivot, jaf-cms, Guppy, Doop and CutePHP. Unfortunately, most of the news is bad - between badly structured code and mixes of HTML and PHP, there was almost nothing good in any of them.
</p>]]></description>
      <pubDate>Fri, 28 Mar 2008 11:10:37 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Stubbles Blog: Traits for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9669</guid>
      <link>http://www.phpdeveloper.org/news/9669</link>
      <description><![CDATA[<p>
On the Stubbles blog, <i>Frank Kleine</i> has <a href="http://www.stubbles.org/archives/42-Traits-for-PHP.html">pointed out</a> a <a href="http://news.php.net/php.internals/35562">proposal</a> from <i>Stefan Marr</i> to include functionality for traits in PHP.
</p>
<blockquote>
As a language construct within PHP it would be very easy to do the same, but easier to learn and to use. Beside some keyword issues (the RFC uses "use" as keyword, but this will of course conflict with <a href="http://php.net/manual/en/language.namespaces.using.php">namespaces</a>) I'm wondering what this will have an impact on reflection - the RFC stays unclear about this. 
</blockquote>
<p>
A trait is a free-floating chink of functionality that, instead of being confined to a class (or file) that has to be called on to use it, exists where the developer can use it from anywhere at any time. This helps solve some of the issues with single inheritance in PHP.
</p>]]></description>
      <pubDate>Wed, 20 Feb 2008 11:17:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[CodeIgniter.com: CodeIgniter 1.6 Hits the Streets]]></title>
      <guid>http://www.phpdeveloper.org/news/9534</guid>
      <link>http://www.phpdeveloper.org/news/9534</link>
      <description><![CDATA[<p>
The latest version of the <a href="http://www.codeigniter.com">CodeIgniter</a> framework has officially been released - version 1.6:
</p>
<blockquote>
EllisLab is proud to announce the release of CodeIgniter 1.6, our open source web application framework.  The release marks a new turn in the development of the framework, and has received considerable attention from both EllisLab developers and the community.
</blockquote>
<p>
There's lots of new features in <a href="http://codeigniter.com/downloads/">this new release</a> including a Database Forge class, improvements to their Active Record implementation, an extendable Model class, and the addition of extendable Helpers.
</p>
<p>
You can find out more about the framework on <a href="http://codeigniter.com">the project's homepage</a> or just head straight to the <a href="http://codeigniter.com/downloads/">downloads section</a> and grab the latest updates.
</p>
]]></description>
      <pubDate>Thu, 31 Jan 2008 07:59:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPWACT.org: Handling UTF-8 with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9483</guid>
      <link>http://www.phpdeveloper.org/news/9483</link>
      <description><![CDATA[<p>
<i>Ed Finkler</i> has pointed out a handy resource for those trying to cope with using the UTF-8 support included in several of PHP's functions - <a href="http://www.phpwact.org/php/i18n/utf-8">this page</a> on the Web Application Component Toolkit wiki.
</p>
<blockquote>
This page is intended as a reference for functionality PHP provides which can either help with handling UTF-8 or should be regarded as a risk when used in conjunction with UTF-8 encoded strings. Further information can be found on the <a href="http://www.phpwact.org/php/i18n">Internationalization (I18N)</a> and <a href="http://www.phpwact.org/php/i18n/charsets">Character Sets / Character Encoding Issues</a> pages.
</blockquote>
<p>
It talks about the "dangerous" functionality PHP has (issues that the language has in current functions) when using things like the PCRE extension, the string extension, the array methods, handling variables, the XML extensions (DOM and SAX), image manipulation, and URL parsing functionality.
</p>]]></description>
      <pubDate>Thu, 24 Jan 2008 07:51:00 -0600</pubDate>
    </item>
  </channel>
</rss>
