<?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, 24 May 2012 19:16:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[RubySource.com: Confessions of a Converted PHP Developer: On Visibility and Privates]]></title>
      <guid>http://www.phpdeveloper.org/news/16331</guid>
      <link>http://www.phpdeveloper.org/news/16331</link>
      <description><![CDATA[<p>
From RubySource.com there's a new post from a confessed developer who moved from PHP to Ruby about <a href="http://rubysource.com/php-developer-on-visibility-and-privates/">PHP's private visibility rules</a> and how they compare to Ruby's.
</p>
<blockquote>
Alright class - today I'm here to talk about the differences and similarities that PHP and Ruby have when it comes to object properties, methods, and their visibility - how you create variables inside classes, and how you can interact with them.
</blockquote>
<p>
He compares the private properties in PHP classes to the corresponding handling in Ruby, including the getters and setters to go with them. There's also a look at class visibility settings in Ruby.
</p>]]></description>
      <pubDate>Thu, 12 May 2011 10:49:52 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Mark van der Velden's Blog: PHP Quiz part 4]]></title>
      <guid>http://www.phpdeveloper.org/news/15370</guid>
      <link>http://www.phpdeveloper.org/news/15370</link>
      <description><![CDATA[<p>
If you were a fan of the <a href="http://phpdeveloper.org/news/12514">PHP</a> <a href="http://phpdeveloper.org/news/13279">quizes</a> that <i>Mark van der Velden</i> has posted in the past, you'll be happy to know he's come back with <a href="http://blog.dynom.nl/archives/PHP-Quiz-part-4_20101102_51.html">part four</a> of the series after a bit of a hiatus.
</p>
<blockquote>
It has been a while, but here is part 4 of the PHP Quiz series! A few questions to crack your brain about, or perhaps you know them all? Try them and find out! Also do read the idea behind these quizzes, here: <a href="http://blog.dynom.nl/archives/The-PHP-Quiz-series_20090925_46.html">The PHP Quiz series</a>
</blockquote>
<p>
In this quiz he tests your knowledge of class visibility, fluent method handling, class extension, strptime and a tricky "for" loop. Take <a href="http://blog.dynom.nl/archives/PHP-Quiz-part-4_20101102_51.html">the quiz</a> and see how you do.
</p>]]></description>
      <pubDate>Tue, 02 Nov 2010 12:05:46 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Wes Shell's Blog: Encapsulation in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/13378</guid>
      <link>http://www.phpdeveloper.org/news/13378</link>
      <description><![CDATA[<p>
<i>Wes Shell</i> has <a href="http://wshell.wordpress.com/2009/10/12/encapsulation-in-php/">posted a new tutorial</a> to his blog today looking at encapsulation in PHP development - containing parts of the script to make them easier to work with as a whole.
</p>
<blockquote>
In order to understand the purpose of encapsulation you first need to  understand the purpose of classes. [...] In order for them to be used properly as they were designed, you will need to limit how users of the class can interact with those characteristics and functionality.
</blockquote>
<p>
He looks at the visibility modifiers (public/private/protected), interface functions and some sample code showing how to use them in a simple class to work with a Person's set of data.
</p>]]></description>
      <pubDate>Tue, 13 Oct 2009 09:05:16 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Chance Garcia's Blog: Visibility and inheritance]]></title>
      <guid>http://www.phpdeveloper.org/news/13031</guid>
      <link>http://www.phpdeveloper.org/news/13031</link>
      <description><![CDATA[<p>
In <a href="http://phpprotip.com/2009/08/visibility-and-inheritance/">this recent post</a> to his blog <i>Chance Garcia</i> looks at visibility and inheritance in PHP applications. Specifically, it references a question that came up on IRC about the "default" visibility for methods and the <a href="http://en.wikipedia.org/wiki/Open/closed_principle">open/closed principle</a>.
</p>
<blockquote>
Out of the whole discussion, here is the points I got (aka understood) out of it. Please correct me in the comments if I'm off base in any way.
</blockquote>
<p>There's two points he makes in the remainder of the post:</p>
<ul>
<li>Methods should only be public when necessary.
<li>Private methods allow you to preserve the class' core functionality.
</ul>
<p>
There's also a bit of code included to illustrate some of his points.
</p>]]></description>
      <pubDate>Wed, 12 Aug 2009 09:40:20 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: More on Private Methods with PHP 5 Member Visibility ]]></title>
      <guid>http://www.phpdeveloper.org/news/10486</guid>
      <link>http://www.phpdeveloper.org/news/10486</link>
      <description><![CDATA[<p>
DevShed finishes off their series looking a private, public and protected variables and methods in classes with <a href="http://www.devshed.com/c/a/PHP/More-on-Private-Methods-with-PHP-5-Member-Visibility/">this final look</a> a private methods in PHP5 object-oriented programming.
</p>
<blockquote>
It's time to leap forward and tackle this final article of the series, which will be focused on covering some additional aspects concerning the use of this kind of class method. In addition, I'll teach you how to utilize the "final" keyword, which is included with PHP 5, to prevent the methods of a specific class from being overridden by any subclass.
</blockquote>
<p>
They work from a <a href="http://www.devshed.com/c/a/PHP/More-on-Private-Methods-with-PHP-5-Member-Visibility/1/">hands-on example</a> to show how they can work with private methods (expanding a bit from last time) and how to use the "final" keyword to restrict any and all modification for a method.
</p>]]></description>
      <pubDate>Wed, 25 Jun 2008 13:58:20 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Defining Public and Protected Methods with Member Visibility in PHP 5]]></title>
      <guid>http://www.phpdeveloper.org/news/10394</guid>
      <link>http://www.phpdeveloper.org/news/10394</link>
      <description><![CDATA[<p>
DevShed continues their series looking at variable scoping in PHP5 classes with <a href="http://www.devshed.com/c/a/PHP/Defining-Public-and-Protected-Methods-with-Member-Visibility-in-PHP-5/">this new look</a> at using the public and protected keywords to "restrict member visibility".
</p>
<blockquote>
Now that you know what will be treated in this fourth chapter of the series, it's time to learn how to declare and implement public and protected methods with PHP 5 classes. Of course, as always I'm going to address this useful topic by using a hands-on approach, which means that there's a bunch of code samples ahead, waiting patiently for you.
</blockquote>
<p>
They talk about calling methods <a href="http://www.devshed.com/c/a/PHP/Defining-Public-and-Protected-Methods-with-Member-Visibility-in-PHP-5/1/">globally</a> first and then move into the keyword restrictions. They show the difference between a public method/variable and a <a href="http://www.devshed.com/c/a/PHP/Defining-Public-and-Protected-Methods-with-Member-Visibility-in-PHP-5/2/">protected</a> one, including how to get at the protected members from a child class.
</p>]]></description>
      <pubDate>Thu, 12 Jun 2008 07:51:13 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Using Subclasses and Accessors with Member Visibility to Protect PHP 5 Class Data]]></title>
      <guid>http://www.phpdeveloper.org/news/10343</guid>
      <link>http://www.phpdeveloper.org/news/10343</link>
      <description><![CDATA[<p>
DevShed has posted the <a href="http://www.devshed.com/c/a/PHP/Using-Subclasses-and-Accessors-with-Member-Visibility-to-Protect-PHP-5-Class-Data/">latest in their series</a> of tutorials covering the scoping keywords in PHP5 (public, private and protected). In this latest edition they work with private values from a parent class.
</p>
<blockquote>
In the last article, I explained how to work with a couple of private properties that partially comprised the API of a basic class, which is useful for saving simple strings to a specified text file.
</blockquote>
<p>
This part builds on this previous example but changes up the subclass (an instance of DataSaver) to use what they call an "accessor" - a function in the parent that returns the private variable/contstant's current value when called.
</p>]]></description>
      <pubDate>Thu, 05 Jun 2008 07:50:08 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Working with Private Properties to Protect PHP 5 Class Data]]></title>
      <guid>http://www.phpdeveloper.org/news/10292</guid>
      <link>http://www.phpdeveloper.org/news/10292</link>
      <description><![CDATA[<p>
DevShed continues their look at the use of the member visibility functionality PHP5 offers in its classes with <a href="http://www.devshed.com/c/a/PHP/Working-with-Private-Properties-to-Protect-PHP-5-Class-Data/">this new part</a> of the series, a look at the private property.
</p>
<blockquote>
One of the most useful features that was introduced into the improved object model of PHP 5 is "member visibility." It provides PHP developers with the ability to specify the level of access each data member of a class will have in the context of a given application.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/PHP/Working-with-Private-Properties-to-Protect-PHP-5-Class-Data/1/">review</a> the other two keywords (public/protected) before venturing on to the <a href="http://www.devshed.com/c/a/PHP/Working-with-Private-Properties-to-Protect-PHP-5-Class-Data/2/">use of "private"</a> to protect, but allow access to, methods and properties in a parent class.
</p>]]></description>
      <pubDate>Thu, 29 May 2008 08:47:04 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Protecting PHP 5 Class Data with Member Visibility]]></title>
      <guid>http://www.phpdeveloper.org/news/10244</guid>
      <link>http://www.phpdeveloper.org/news/10244</link>
      <description><![CDATA[<p>
In <a href="http://www.devshed.com/c/a/PHP/Protecting-PHP-5-Class-Data-with-Member-Visibility/">this new tutorial</a> posted to DevShed, they take a look at working with classes in PHP5, specifically using the keywords for "member visibility" to make your classes a bit more structured.
</p>
<blockquote>
The previous concept can also be applied successfully when it comes to defining the visibility of properties and methods in PHP classes. [...] Using the jargon of object-oriented programming, this capacity is widely known as member visibility. This capacity allows PHP programmers to establish whether the set of methods and properties of a specific class will be public, protected, or private.
</blockquote>
<p>
They start more generally by looking at how to set up the variables <a href="http://www.devshed.com/c/a/PHP/Protecting-PHP-5-Class-Data-with-Member-Visibility/1/">globally</a> and then move down the line talking about <a href="http://www.devshed.com/c/a/PHP/Protecting-PHP-5-Class-Data-with-Member-Visibility/2/">restrictions</a> (private/protected/public) and how to <a href="http://www.devshed.com/c/a/PHP/Protecting-PHP-5-Class-Data-with-Member-Visibility/3/">get to them</a> in the scripts outside the class.
</p>]]></description>
      <pubDate>Thu, 22 May 2008 09:37:05 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[JSLabs:  Wordpress seo: 5 tips for improving search engine visibility]]></title>
      <guid>http://www.phpdeveloper.org/news/9109</guid>
      <link>http://www.phpdeveloper.org/news/9109</link>
      <description><![CDATA[<p>
The JSLabs blog has <a href="http://www.whenpenguinsattack.com/2007/11/25/wordpress-seo-5-tips-for-improving-search-engine-visibility/">five quick tips</a> for WordPress users out there on how to make their blogs a bit more "search engine friendly".
</p>
<blockquote>
The following are 5 changes you can make to your wordpress blog that can improve your search engine visibility.
</blockquote>
<p>The methods on the list are:</p>
<ul>
<li>Permalinks
<li>Create a sitemap
<li>Improve the titles of your articles
<li>Site submissions
<li>Tagging & Meta Keywords
</ul>
<p>
Details are given on each on implementation.
</p>]]></description>
      <pubDate>Mon, 26 Nov 2007 07:54:00 -0600</pubDate>
    </item>
  </channel>
</rss>

