<?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>Sat, 18 May 2013 04:37:27 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Using the Stack Exchange API with PHP (part 1)]]></title>
      <guid>http://www.phpdeveloper.org/news/15659</guid>
      <link>http://www.phpdeveloper.org/news/15659</link>
      <description><![CDATA[<p>
On the Zend Developer Zone today the <a href="http://devzone.zend.com/article/12829-Using-the-Stack-Exchange-API-with-PHP-part-1">first part of a series</a> from <i>Vikram Vaswani</i> has been posted. This new set of articles will look at how to use the Stack Exchange API from your PHP applications.
</p>
<blockquote>
The thing about Stack Overflow, though, is that it has a geeky secret of its own. Like many Web 2.0 applications, it exposes its data to the public via the Stack Exchange Web service API, making it possible to develop customized applications that run on top of the base service. This API allows access to a number of important functions, including searching for questions, retrieving answers and comments, accessing user profiles, and working with tags and badges. It's also pretty easy to integrate this API into a PHP application - and this two-part article will show you how!
</blockquote>
<p>
In <a href="http://devzone.zend.com/article/12829-Using-the-Stack-Exchange-API-with-PHP-part-1">part one</a> he introduces you to some of the conventions and tips you'll need to know when reading through the article. He shows how to get and parse a sample response (with <a href="http://php.net/json_decode">json_decode</a>). He also uses the proposed <a href="http://pear.php.net/pepr/pepr-proposal-show.php?id=647">StackPHP</a> PEAR package to make requests for general question information, specific details, tags, comments and search results.
</p>]]></description>
      <pubDate>Thu, 30 Dec 2010 13:04:02 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Stas Malyshev' Blog: On PHP features]]></title>
      <guid>http://www.phpdeveloper.org/news/15637</guid>
      <link>http://www.phpdeveloper.org/news/15637</link>
      <description><![CDATA[<p>
<i>Stas Malyshev</i> has <a href="http://php100.wordpress.com/2010/12/25/on-php-feature/">a new post to his blog</a> points out the post he made over on <a href="http://phpdeveloper.org/news/15605">StackExchange</a> asking developers what features they'd like to see in upcoming versions of PHP (with over 70 people responding).
</p>
<blockquote>
Corollary of that is that some clever tricks are better left not done and some cool things may not look that cool when you have to deal with the consequences. That being said, I think there are many cool things yet to be done in PHP. So, I've posted a poll on Programmers.StackExchange site about what people want to see in PHP. I know people regularly post on PHP lists about that, etc. but I think SE crowd would be somewhat different from what is found on PHP internal lists, so it would be interesting to see what people's wishlists for PHP are.
</blockquote>
<p>
Among the suggestions on the list there's things like: named parameters, an effort to make PHP more truly OOP, better Unicode support - even a <a href="http://code.google.com/p/pihipi/">working parser</a> someone created to address some of the common concerns about the language. It's good to see some commentors coming back at some of the suggestions with their own opinions too.
</p>]]></description>
      <pubDate>Mon, 27 Dec 2010 09:58:39 -0600</pubDate>
    </item>
  </channel>
</rss>
