<?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, 23 May 2013 01:01:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Documentation Makes the World Go Round]]></title>
      <guid>http://www.phpdeveloper.org/news/16945</guid>
      <link>http://www.phpdeveloper.org/news/16945</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new article emphasizing something that lots of developers forget to make a part of their process when writing code - <a href="http://phpmaster.com/documentation-makes-the-world-go-round/">creating useful documentation</a> to help make your code that much clearer.
</p>
<blockquote>
If you're writing code that will be shared with others, put yourself in their shoes. Don't let your project lose potential users, community members, and possible contributors all because of insufficient documentation.
</blockquote>
<p>
He (<i>Matthew Turland</i>) suggests a few things to keep in mind as you're writing up your documentation - the content is "king" (an emphasis on good descriptions/examples/use cases), open it up to external contributions using things like wikis (or even stored in the source code repository) and a focus on technical writing skills. Even the best tools out there can suffer if there's poor or no documentation.
</p>]]></description>
      <pubDate>Tue, 04 Oct 2011 09:03:16 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Kristina Chodorow's Blog: Writing a PHP Extension (Four Part Series)]]></title>
      <guid>http://www.phpdeveloper.org/news/16737</guid>
      <link>http://www.phpdeveloper.org/news/16737</link>
      <description><![CDATA[<p>
<i>Kristina Chodorow</i> has posted a four part series of articles to her blog that shares some of her experiences in developing an extension for PHP (on C/C++). It walks you through the entire process - from the basic "hello world" out to working with more complex data structures.
</p>
<blockquote>
A PHP extension allows you to connect almost any C/C++ code you want to PHP. This is a 4-part tutorial on how to write an extension. [...] Almost all of the code examples in this tutorial are available on <a href="https://github.com/kchodorow/rlyeh">Github</a>.
</blockquote>
<p>The parts of the series cover:</p>
<ul>
<li><a href="http://www.snailinaturtleneck.com/blog/2011/08/11/php-extensions-made-eldrich-installing-php/">setting up a PHP environment</a>
<li>creating a <a href="http://www.snailinaturtleneck.com/blog/?p=1520">first "hello world" extension</a>
<li><a href="http://www.snailinaturtleneck.com/blog/?p=1521">working with the PHP C API</a>
<li><a href="http://www.snailinaturtleneck.com/blog/?p=1522">creating PHP objects in C</a> (classes)
</ul>
<p>
Each step comes with some good explanation, code samples and some advice on common tasks and pitfalls along the way.
</p>]]></description>
      <pubDate>Thu, 18 Aug 2011 10:29:37 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Ibuildings techPortal: DPCRadio: Technical Writing]]></title>
      <guid>http://www.phpdeveloper.org/news/16270</guid>
      <link>http://www.phpdeveloper.org/news/16270</link>
      <description><![CDATA[<p>
On the Ibuildings techPortal they've posted a new episode of their recordings from the Dutch PHP Conference 2010, DPCRadio - a recording of <i>Elizabeth Naramore</i>'s session <a href="http://techportal.ibuildings.com/2011/04/28/dpcradio-technical-writing/">Technical Writing</a>.
</p>
<blockquote>
If you've had an idea for writing a blog post or article, but you're not sure where to start, this talk is for you! Maybe you've had difficulty effectively documenting your code, or communicating your ideas to non-techies. This talk will help you, too! In this fun and informative session, we'll discuss the basics of writing and clear communication through the written word. We'll also talk about strategies for keeping your writing interesting and informative at the same time. Finally, we'll discuss resources for improving your writing skills in the future.
</blockquote>
<p>
You can either use the <a href="http://techportal.ibuildings.com/2011/04/28/dpcradio-technical-writing/">in-page player</a> to listen or you can <a href="http://dpcradio.s3.amazonaws.com/2010_018.mp3">download the mp3</a> to listen wherever you'd like.
</p>]]></description>
      <pubDate>Fri, 29 Apr 2011 08:56:26 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Reading, Writing and Creating Files in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6116</guid>
      <link>http://www.phpdeveloper.org/news/6116</link>
      <description><![CDATA[<p>
DevShed has <a href="http://www.devshed.com/c/a/PHP/Reading-Writing-and-Creating-Files-in-PHP/">a new tutorial</a> posted today with a look at one of the more common tasks performed with PHP (second to generating web pages, of course) - working with files. It can be a little tricky for a budding PHP programmer, but they've got the info you need to get started.
</p>
<blockquote>
Reading and writing to files can be useful if you do not require the storing of important data, such as a web counter. I must warn you though, that this method of storage should not be used to store passwords and other critical information, as it is not safe. Here we will discuss how to handle files and directories in PHP, specifically, how to create, read and write them.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/PHP/Reading-Writing-and-Creating-Files-in-PHP/">start off with a look</a> at file permissions on both Unix and Windows systems ot give you an idea of what problems they could cause. Then, it's on to the actual files themselves - for this part, though, they only look at reading them in and working with their contents.
</p>]]></description>
      <pubDate>Wed, 23 Aug 2006 08:59:30 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Sara Golemon's Blog: The government will disavow any knowledge of your existence.]]></title>
      <guid>http://www.phpdeveloper.org/news/5863</guid>
      <link>http://www.phpdeveloper.org/news/5863</link>
      <description><![CDATA[<p>
If you were planning on attending the <a href="http://www.phparch.com/works">php|works conference</a> in the fall and getting to hear <i>Sara Golemon</i> talk on extensions, you might just have to wait. According to <a href="http://blog.libssh2.org/index.php?/archives/33-The-government-will-disavow-any-knowledge-of-your-existence..html">her latest post</a>, things haven't gone well with her passport situation.
</p>
<blockquote>
<p>
So awhile ago I announced that I'd be speaking at php|works including a 3-hour workshop on extension writing. Knowing that the conference was outside of the US I made sure to apply for my passport well in advance (four months to be precise). 
</p>
<p>
Well, long story short, the lovely folks at the state department must have confused 'Sara' with 'Syria' because I've been fighting them over the issuance of my passport ever since.
</p>
</blockquote>
<p>
All is not lost, though - since the show must go on, <i>Sara</i> has found two people to take over her two talks (the <a href="http://hades.phparch.com/ceres/public/page/index.php/works::schedule::synopses::extending_php">extension talk</a> and one on <a href="http://hades.phparch.com/ceres/public/page/index.php/works::schedule::synopses::microsoft_platforms_for_the_php_developer">PDO_User</a>). 
</p>]]></description>
      <pubDate>Tue, 25 Jul 2006 05:35:47 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Marcus Whitney's Blog: A/R/T Is Seeking Columnists]]></title>
      <guid>http://www.phpdeveloper.org/news/5623</guid>
      <link>http://www.phpdeveloper.org/news/5623</link>
      <description><![CDATA[<p>
<i>Marcus Whitney</i> has a quick note today <a href="http://www.marcuswhitney.com/?p=89">on his blog</a> about php|architect's search for columnists to write for their <a href="http://hades.phparch.com/artemis/main">A/R/T article repository</a>.
</p>
<blockquote>
Just a heads up to all you incredible PHP writers out there. I am actively looking for columnists to contribute to A/R/T on a weekly, bi-weekly and monthly basis. If you want to get lots of paid experience as a technical writer, contact me at marcus-AT-phparch.com. Thanks.
</blockquote>
<p>
Check out <a href="http://hades.phparch.com/artemis/main">some of the current articles</a> already posted there to get an idea of what they're looking for - things like <a href="http://hades.phparch.com/ceres/public/article/index.php/art::ajax::ajax_rating_system">Writing an Ajax-based Visual Rating System with PHP</a> and <a href="http://hades.phparch.com/ceres/public/article/index.php/art::cakephp::overview">An Overview of the CakePHP Framework</a>.
</p>]]></description>
      <pubDate>Mon, 19 Jun 2006 13:44:58 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend: Extension Writing Tutorials - Resources (Part 3)]]></title>
      <guid>http://www.phpdeveloper.org/news/5361</guid>
      <link>http://www.phpdeveloper.org/news/5361</link>
      <description><![CDATA[<p>
The Zend site has published <a href="http://www.zend.com/php/internals/extension-writing3.php">part three</a> of their "Extension Writing" tutorials, this time focusing on the management of resources in your extensions.
</p>
<quote>
<i>
Up until now, you've worked with concepts that are familiar and map easily to userspace analogies. In this tutorial, you'll dig into the inner workings of a more alien data type - completely opaque in userspace, but with behavior that should ultimately inspire a sense of deja vu.
</i>
</quote>
<p>
They <a href="http://www.zend.com/php/internals/extension-writing3.php">start things off</a> by describing what resources are in the Zend Engine, initializing your resources, using them, and destroying them. They mention different kinds of resources, including normal and persistent resources. There's code for each step of the way, including a sanity check at the end.
</p>]]></description>
      <pubDate>Fri, 12 May 2006 16:30:46 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[IBM developerWorks: Reading and writing the XML DOM with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/4466</guid>
      <link>http://www.phpdeveloper.org/news/4466</link>
      <description><![CDATA[On the IBM developerWorks page today, there's <a href="http://www-128.ibm.com/developerworks/opensource/library/os-xmldomphp/">this new tutorial</a> dealing with reading and writing XML with the DOM functionality in PHP.
<p>
<quote>
<i>
Myriad techniques are available for reading and writing XML in PHP. This article presents three methods for reading XML: using the DOM library, using the SAX parser, and using regular expressions. Writing XML using DOM and PHP text templating will also be covered.
</i>
</quote>
<p>
They <a href="http://www-128.ibm.com/developerworks/opensource/library/os-xmldomphp/">look at</a> what XML is, how to read it into PHP (with examples of DOM, SAX parsers, and regular expression methods), and writing out XML. The DOM functionality that they use for the examples is the newer, PHP5-compatable methods...]]></description>
      <pubDate>Thu, 08 Dec 2005 08:18:57 -0600</pubDate>
    </item>
  </channel>
</rss>
