<?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, 24 May 2013 16:56:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Kae Verens' Blog: Extracting a sudoku puzzle from a photo]]></title>
      <guid>http://www.phpdeveloper.org/news/11881</guid>
      <link>http://www.phpdeveloper.org/news/11881</link>
      <description><![CDATA[<p>
<i>Kae Verens</i> has posted a <a href="http://verens.com/archives/2009/02/03/extracting-a-sudoku-puzzle-from-a-photo/">cool little application</a> of how to pull information out of a photo and parse it with the GD library. His example is a <a href="http://verens.com/archives/2009/02/02/visual-sudoku-solver/">visual sudoku solver</a> (part one, at least).
</p>
<blockquote>
The plan for this one is that, if you're doing a sudoku puzzle in the pub or on the train, and you get stuck, you just take a snapshot of the puzzle with your camera-phone, send the photo to a certain mobile number, and a few seconds later the solution is sent back as an SMS message. The solution costs you something small - 50 cents, maybe.
</blockquote>
<p>
The script looks at a picture of a sudoku puzzle, converts it to b&w and tries to find the squares surrounding each position of the board. With these measurements, the next step is to grab the numbers already in the puzzle and hand those off to the puzzle solver to be processed.
</p>]]></description>
      <pubDate>Wed, 04 Feb 2009 12:57:18 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Douglas Brown's Blog: Quick Methods Used for Solving PHP Errors]]></title>
      <guid>http://www.phpdeveloper.org/news/11637</guid>
      <link>http://www.phpdeveloper.org/news/11637</link>
      <description><![CDATA[<p>
<i>Douglas Brown</i> has <a href="http://www.brownphp.com/2008/12/quick-methods-used-for-solving-php-errors/">posted some hints</a> to help you find errors in your PHP scripts all centered around error reporting settings.
</p>
<blockquote>
There are several methods to solve errors in PHP code. Sometimes when the user waits to see an output a blank page will be shown if there is an error. To show the errors E_ALL^E_STRICT is used for the PHP 5 version. Contrarily, remaining versions just use E_ALL.
</blockquote>
<p>
He talks about the log_errors and display_errors settings in your php.ini, the <a href="http://php.net/error_reporting">error_reporting</a> function call or a custom error handler as shown <a href="http://us2.php.net/manual/en/function.error-reporting.php#73759">in this example</a> from the PHP manual.
</p>]]></description>
      <pubDate>Tue, 30 Dec 2008 07:57:21 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Sean Coates' Blog: Actually Solving a Problem (believe it or not)]]></title>
      <guid>http://www.phpdeveloper.org/news/9200</guid>
      <link>http://www.phpdeveloper.org/news/9200</link>
      <description><![CDATA[<p>
<i>Sean Coates</i> has <a href="http://blog.phpdoc.info/archives/86-Actually-Solving-a-Problem-believe-it-or-not.html">posted a new item</a> on his blog today applauding <i>Greg Beaver</i> for comments made on the <a href="http://news.php.net/php.internals">php.internals</a> mailing list concerning the ongoing namespace deliberations.
</p>
<blockquote>
In a time where <a href="http://news.php.net/php.internals">php.internals</a> is becoming more and more useless due to an increasingly poor signal to noise ratio, Greg has stepped up and intelligently <a href="http://news.php.net/php.internals/33816">addressed the ongoing namespace debate</a> in a way that not only shows that he's done his homework, but delivers a much needed stomp onto the toes of many of the other posters, who, quite frankly, are talking out of their a$$es.
</blockquote>
<p>
<i>Greg</i> has <a href="http://news.php.net/php.internals/338">summarized things</a> in a six point list of recommendations for the implementation of namespaces for the language (including some dangers of their potential use).
</p>]]></description>
      <pubDate>Fri, 07 Dec 2007 15:24:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Nick Halstead's Blog: Solving Programming Problems]]></title>
      <guid>http://www.phpdeveloper.org/news/8104</guid>
      <link>http://www.phpdeveloper.org/news/8104</link>
      <description><![CDATA[<p>
On his blog, <i>Nick Halstead</i> <a href="http://blog.assembleron.com/2007/06/21/solving-programming-problems/">shares a few tips</a> he's worked up to help developers that might be having a hard time with coding issues - a few steps towards solving programming problems.
</p>
<blockquote>
Early on in most people's programming careers problem solving is a large part of your day to day job. As you become more experienced you find that many programming patterns that you have used before can be reapplied. You then start working on larger and larger projects and the problems tend to be more about solving architectural problems rather than logic related ones.
</blockquote>
<p>
Included in <a href="http://blog.assembleron.com/2007/06/21/solving-programming-problems/">his list</a> are things like "Talking it through", "Brainstorming", "Breaking it down" and "Research". This last one can be one of the most important and can save tons of time in the long run. With tools like Google and other sites, there's no reason to check before you start a project to see if there's someone out there that might have already done it (and it might be more well developed).
</p>]]></description>
      <pubDate>Fri, 22 Jun 2007 10:11:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Nick Halstead's Blog: PHP Programming Contest - Win Zend Studio]]></title>
      <guid>http://www.phpdeveloper.org/news/8042</guid>
      <link>http://www.phpdeveloper.org/news/8042</link>
      <description><![CDATA[<p>
<i>Nick Halstead</i> has <a href="http://blog.assembleron.com/2007/06/14/php-programming-contest-win-zend-studio/">announced a contest</a> on his blog today for PHP developers everywhere to participate in - a programming competition surrounding a challenge he's created.
</p>
<blockquote>
It has been a lot harder than I thought to come up with a fair programming challenge that would not take too long or require lots of knowledge in any particular framework or other associated technology. It could have been to make use of a whole host of currently available API's and to make a useful mash-up but these again require other external knowledge beyond just PHP. I finally settled on a logic problem that is hopefully not too hard to solve but will test a range of PHP skills.
</blockquote>
<p>
The <a href="http://blog.assembleron.com/2007/06/14/php-programming-contest-win-zend-studio/">problem he's worked up</a> involves changing a word, one letter at a time, into another word using user-defined lists and choice of word. There's several requirements you'll need to follow an d rules for things like the submission process and what server setup can be used.
</p>
<p>
So, what's the motivation? First prize is a copy of <a href="http://www.zend.com/products/zend_studio?hpb=4">Zend Studio Professional</a> and a year of support, second prize is a <a href="http://www.zend.com/store/zend_php_extras/framework_shirt">Zend t-shirt</a>, and third is a Zend Pen. For full information on participating and on all of the rules you'll need to follow, check out <a href="http://blog.assembleron.com/2007/06/14/php-programming-contest-win-zend-studio/">Nick's full post</a>.
</p>]]></description>
      <pubDate>Thu, 14 Jun 2007 07:11:13 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[ProWebDeveloper.info: Reducing Database Load with Secure Client-side Sessions]]></title>
      <guid>http://www.phpdeveloper.org/news/7290</guid>
      <link>http://www.phpdeveloper.org/news/7290</link>
      <description><![CDATA[<p>
On prowebdeveloper.info, <i>Marcel Esser</i> has posted the <a href="http://www.prowebdeveloper.info/node/2">first in a series</a> of articles looking at functionality to reduce database load in applications, specifically those using secure client-side sessions.
</p>
<blockquote>
Scaling web applications is easy. Generally, if a web application is designed to store all of its session information in a database, it can be easily scaled by adding more servers in a load-balanced setup. This is tried and true, and it works very well - until your database server runs out of capacity.
</blockquote>
<p>
He <a href="http://www.prowebdeveloper.info/node/2">lists the common ways</a> most developers solve this problem (four of them) but notes that thay are more of a temporary solution rather than a long-term fix. Instead, he outlines what the requirements for a library to correctly handle the connections should be and explains how each of them would be implemented. He's been following this kind of mentality in the development of his own package - <a href="http://www.prowebdeveloper.info/prowebcomponents/">proWebComponents</a>.
</p>]]></description>
      <pubDate>Fri, 16 Feb 2007 08:02:00 -0600</pubDate>
    </item>
  </channel>
</rss>
