<?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, 20 Nov 2008 04:56:04 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Micheal Kimsal's Blog: Symfony __toString() generation]]></title>
      <guid>http://www.phpdeveloper.org/news/10865</guid>
      <link>http://www.phpdeveloper.org/news/10865</link>
      <description><![CDATA[<p>
<i>Michael Kimsal</i> has <A href="http://michaelkimsal.com/blog/symfony-__tostring-generation/">pointed out</a> a small irritation when using the Symfony framework and models - an issue when using models that have relationships.
</p>
<blockquote>
If there are relations (an Author has a Book, for example). the generated forms will complain that the generated Models need a __toString() method to be used in the Form/View.  In grails, this is the case, but every domain (corresponding to a Symfony 'model') has an implicit toString() method already generated, which return the string "<domain>:<id>".  For most production work, you'll want to override it with whatever you need the string to read, but for prototyping, it's fine.
</blockquote>
<p>
He went in and modified the Symfony core to add in a __toString call that would return the object correctly. Several of the commentors agree with his frustration and some of the Symfony developers even chime in with some of the reasoning behind why it's like that.
</p>]]></description>
      <pubDate>Wed, 20 Aug 2008 11:14:50 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Patrick Reilly's Blog: Join the PHP Evangelism Team - Mailing List]]></title>
      <guid>http://www.phpdeveloper.org/news/8881</guid>
      <link>http://www.phpdeveloper.org/news/8881</link>
      <description><![CDATA[<p>
<i>Patrick Reilly</i> has <a href="http://www.surripui.net/2007/10/22/join-the-php-evangelism-team-mailing-list/">posted about</a> a new group that's being formed in the PHP world - a PHP Evangelism Team designed to help promote the language.
</p>
<blockquote>
The goal of the PHP Evangelism Team is to bring together the right people, resources and experience from across the PHP Community to provide developers with the process guidance and best practices needed to create new opportunities for the web.
</blockquote>
<p>
They're also looking to <a href="http://www.surripui.net/2007/10/22/join-the-php-evangelism-team-mailing-list/">help support</a> local user groups and aid in any PHP-related event they can. You can subscribe to their mailing list to get more information as the group develops. Check out the post for the address to join the list.
</p>]]></description>
      <pubDate>Mon, 22 Oct 2007 13:31:43 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[IBM developerWorks: Turn SQL into XML with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/8326</guid>
      <link>http://www.phpdeveloper.org/news/8326</link>
      <description><![CDATA[<p>
On the IBM developerWorks site today, there's a <a href="http://www.ibm.com/developerworks/xml/library/x-query2xml/index.html">new tutorial</a> by <i>Vikram Vaswani</i> walking through the use of the <a href="http://pear.php.net/package/XML_Query2XML/">XML_Query2XML PEAR package</a> to pull data from your SQL database and push it into an XML structure.
</p> 
<blockquote>
Ever wished for an easy way to transform SQL result sets into XML? It's a PEAR package named XML_Query2XML, and it provides a comprehensive framework to efficiently turn the results of a database query into a customizable XML document. This article introduces the package, and demonstrates useful real-world applications, including using it with XSL and XPath, combining it with data from external Web services, and creating database dump files.
</blockquote>
<p>
They <a href="http://www.ibm.com/developerworks/xml/library/x-query2xml/index.html">go through</a> the installation and the steps to create the XML:
</p>
<ul>
<li>Convert SQL to XML
<li>Transform XML output with XSL
<li>Customize XML output
<li>Work with SQL joins
<li>Filter SQL records with XPath
<li>Merge data from multiple sources
<li>Create database backups
</ul>
<p>
Check out <a href="http://www.ibm.com/developerworks/xml/library/x-query2xml/index.html">the full tutorial</a> for an excellent guide to using this powerful PEAR package.
</p>]]></description>
      <pubDate>Wed, 25 Jul 2007 09:21:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Splitbrain.org: Joining .WAVs with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6770</guid>
      <link>http://www.phpdeveloper.org/news/6770</link>
      <description><![CDATA[<p>
In <a href="http://www.splitbrain.org/blog/2006-11/15-joining_wavs_with_php">this new post</a> from the splitbrain.org website (creators of the <a href="http://www.splitbrain.org/projects/dokuwiki">Dokuwiki</a> application), there's an example of how to join wav files together with PHP with a quick and easy script.
</p>
<blockquote>
I'm currently working on a <a href="http://wiki.splitbrain.org/plugin%3Acaptcha">CAPTCHA plugin</a> for <a href="http://www.splitbrain.org/projects/dokuwiki">DokuWiki</a> and thought about providing audio output for users not able to see the image. This is pretty simple for CAPTCHAs - there is no need for complicated speech synthesis because you only need recordings of the 26 possible letters. But you need a way of joining those recordings on the fly...
</blockquote>
<p>
There was an example he found <a href="http://articles.techrepublic.com.com/5100-3513-5810215.html">previously</a>, but it seemed like overkill, so he rolled together his own solution - a 24 line script that takes in the filenames of the wav files and spits back out the joined resource. This functionality has already been added to <a href="http://wiki.splitbrain.org/plugin%3Acaptcha">the CAPTCHA plugin</a> if you'd like to check it out.
</p>]]></description>
      <pubDate>Mon, 27 Nov 2006 08:50:00 -0600</pubDate>
    </item>
  </channel>
</rss>
