<?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>Tue, 21 May 2013 23:29:41 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lukas Smith's Blog: Symfony2, what I think is still left to do]]></title>
      <guid>http://www.phpdeveloper.org/news/16216</guid>
      <link>http://www.phpdeveloper.org/news/16216</link>
      <description><![CDATA[<p>
<i>Lukas Smith</i> has posted some of the things he thinks the <a href="http://pooteeweet.org/blog/0/1924#m1924">Symfony2 framework still has left</a> to do before it can be released in a stable form.
</p>
<blockquote>
The goal of this blog post is to number one serve me as a todo list of stuff that I personally think needs to be fixed before Symfony2 can be released. Hopefully it will also entice some people to help out with these tasks. I am focusing on the medium to large tasks. There are of course still a fair number of smaller fixes that need to be applied.
</blockquote>
<p>Items on the list include:</p>
<ul>
<li>switch Security/Validation components to using message key's rather than full sentences
<li>Assetic documentation
<li>Adding a DIC aware Serializer
<li>Better support for SSL'ed urls and assets
<li>ttempt to automatically determine service scopes
</ul>]]></description>
      <pubDate>Tue, 19 Apr 2011 09:05:11 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[FuelPHP: Oil Migrations, Tasks and Console (Screencast)]]></title>
      <guid>http://www.phpdeveloper.org/news/16046</guid>
      <link>http://www.phpdeveloper.org/news/16046</link>
      <description><![CDATA[<p>
<i>Phil Sturgeon</i> has <a href="http://blip.tv/file/4885416">put together a screencast</a> showing off a few of the features of the <a href="http://fuelphp.com">Fuel PHP framework</a> like migrations, tasks and the console the Oil tool provides.
</p>
<blockquote>
In this video I'm going to be demonstrating migrations which I touched on in the last video but I felt I should go into them in more depth. Migrations [...] are essentially a way to stage changes for your database in a way that means the changes can be independent from the schema as a whole.
</blockquote>
<p>
He walks you through the creation of a migration with the help of the Oil command line tool. The generated classes include "up" and "down" methods for the creation and rollback of your changes. He shows the process to create a simple task and how to use the built-in console to interactively work with the framework. You can find out more about Fuel <a href="http://fuelphp.com/docs/">on the Fuel documentation section</a> of the project's site.
</p>]]></description>
      <pubDate>Tue, 15 Mar 2011 11:31:39 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Performing Basic Tasks with MySQL 4.1 and Above, using mysqli with PHP 5]]></title>
      <guid>http://www.phpdeveloper.org/news/5735</guid>
      <link>http://www.phpdeveloper.org/news/5735</link>
      <description><![CDATA[<p>
In <a href="http://www.devshed.com/c/a/MySQL/Performing-Basic-Tasks-with-MySQL-4-and-Above-using-mysqli-with-PHP-5/">this new tutorial</a> from DevShed today, they look at a method of accessing a MySQL database that doesn't seem to be discussed as much - <a href="http://www.php.net/mysqli">mysqli</a>.
</p>
<blockquote>
All right, I know that you're now saying that's not breaking news, since the implementation of objects is an old programming feature. However, PHP 5 has a lot more to offer when it comes to using MySQL. If you're using MySQL 4.1 and above, the good news is that PHP 5 offers a fairly comprehensive extension, called "mysqli," which allows you to interact natively with MySQL via an object-based approach, aside from taking advantage of the new functionality provided by the database server.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/MySQL/Performing-Basic-Tasks-with-MySQL-4-and-Above-using-mysqli-with-PHP-5/">start with</a> a basic introduction of the extension, including how to perform some of the basic bits of functionality on your MySQL database - connecting, getting host information, and even performing a simple query. They then get into the "real power" behind the mysqli extension, the ability to run multiple queries and handle natively the results of those queries easily. They wrap it all up with a look at using prepared statements with this extension, showing the prepare, bind_param, and execute functions.
</p>]]></description>
      <pubDate>Fri, 30 Jun 2006 12:14:47 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Paul Jones' Blog: Automating Release Tasks]]></title>
      <guid>http://www.phpdeveloper.org/news/5158</guid>
      <link>http://www.phpdeveloper.org/news/5158</link>
      <description><![CDATA[<p>
<i>Paul Jones</i>, author for the popular <a href="http://solarphp.com/">Solar</a> PHP framework, has posted the <a href="http://paul-m-jones.com/blog/?p=204">secret to his success</a> of being able to release five versions of the framework in seven days - an automatic release process.
</p>
<quote>
<i>
<p>
But what I want to talk about in this entry is the release process itself. With the help of Greg Beaver (indirectly) and Clay Loveless (directly), Solar now has a moderate-length PHP script that handles almost all aspects of the release process automatically. Usage is at the command line; issue "php release.php" for a test run, or "php release.php commit" for a full release-and-commit cycle.
</p>
<p>
With any luck, the lessons I've learned here will be of use to someone else; with more luck, perhaps someone else will see possible improvements and mention them here. Read on for a narrative of how the script came to be.
</p>
</i>
</quote>
<p>
He not only talks about the package, he also <a href="http://paul-m-jones.com/blog/?p=204">goes through</a> the three iterations that it took to get the package where it is today. It has evolved from a simple PEAR package, to an automatically adjusting PEAR package, and enhancing it to add administrative functionality to maintaining it. He notes that there are still a few manual tasks that have to be done, but overall, it's a nice and easy process.
</p>]]></description>
      <pubDate>Wed, 12 Apr 2006 07:07:41 -0500</pubDate>
    </item>
  </channel>
</rss>
