<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Ok&#8230; I&#8217;m gonna change the damned thing then!</title>
	<atom:link href="http://www.codedivision.com/modules/wordpress/2004/07/24/ok-im-gonna-change-the-damned-thing-then/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codedivision.com/modules/wordpress/2004/07/24/ok-im-gonna-change-the-damned-thing-then/</link>
	<description></description>
	<lastBuildDate>Wed, 29 Apr 2009 09:09:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tiran Kenja</title>
		<link>http://www.codedivision.com/modules/wordpress/2004/07/24/ok-im-gonna-change-the-damned-thing-then/comment-page-1/#comment-2</link>
		<dc:creator>Tiran Kenja</dc:creator>
		<pubDate>Tue, 27 Jul 2004 22:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.codedivision.com/modules/wordpress/?p=4#comment-2</guid>
		<description>Yeah. it is actually. But it&#039;s better. Putting each kind of data into separate objects is how you do OOP. And right now the bBlog object is not data centric. It&#039;s centered around making bBlog functions work. Much like in classic procedural programming.

It is - however - nice that you do everything through one object. Since I can overwrite what I need on it. Would be better if user info was stored and accessed through a separate object tho. Since when integrating it with a CMS you will have to use the CMS users and not the ones bBlog knows about.</description>
		<content:encoded><![CDATA[<p>Yeah. it is actually. But it&#8217;s better. Putting each kind of data into separate objects is how you do OOP. And right now the bBlog object is not data centric. It&#8217;s centered around making bBlog functions work. Much like in classic procedural programming.</p>
<p>It is &#8211; however &#8211; nice that you do everything through one object. Since I can overwrite what I need on it. Would be better if user info was stored and accessed through a separate object tho. Since when integrating it with a CMS you will have to use the CMS users and not the ones bBlog knows about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eaden McKee</title>
		<link>http://www.codedivision.com/modules/wordpress/2004/07/24/ok-im-gonna-change-the-damned-thing-then/comment-page-1/#comment-1</link>
		<dc:creator>Eaden McKee</dc:creator>
		<pubDate>Tue, 27 Jul 2004 02:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.codedivision.com/modules/wordpress/?p=4#comment-1</guid>
		<description>Re OO code.. so now that you&#039;ve submitted the patch, is it still horrible OO code?

Re xml-rpc, the xmlrpc.php file is INCOMPLETE and doesn&#039;t support the blogger API yet. </description>
		<content:encoded><![CDATA[<p>Re OO code.. so now that you&#8217;ve submitted the patch, is it still horrible OO code?</p>
<p>Re xml-rpc, the xmlrpc.php file is INCOMPLETE and doesn&#8217;t support the blogger API yet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

