<?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: Building a Zend Modular CMS System – Part 5 Navigation and Blocks</title>
	<atom:link href="http://steven.macintyre.name/building-a-zend-modular-cms-system-%e2%80%93-part-5-navigation-and-blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://steven.macintyre.name/building-a-zend-modular-cms-system-%e2%80%93-part-5-navigation-and-blocks/</link>
	<description>Life. Work. Sex. Social. Technology. Anything and more</description>
	<lastBuildDate>Tue, 31 Aug 2010 08:38:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Chris</title>
		<link>http://steven.macintyre.name/building-a-zend-modular-cms-system-%e2%80%93-part-5-navigation-and-blocks/comment-page-1/#comment-1208</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 07 Sep 2009 17:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://steven.macintyre.name/?p=2788#comment-1208</guid>
		<description>I like this handling of Blocks.

To improve on how you implement your blocks, I would create a Block interface to enforce available functions in Block class implementations.

In your class &#039;Ig_View_Helper_DrawBlock&#039;, I don&#039;t think $this-&gt;db is declared anywhere ($params is declared but not $db). Just a best practices thing.</description>
		<content:encoded><![CDATA[<p>I like this handling of Blocks.</p>
<p>To improve on how you implement your blocks, I would create a Block interface to enforce available functions in Block class implementations.</p>
<p>In your class &#8216;Ig_View_Helper_DrawBlock&#8217;, I don&#8217;t think $this-&gt;db is declared anywhere ($params is declared but not $db). Just a best practices thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: craig</title>
		<link>http://steven.macintyre.name/building-a-zend-modular-cms-system-%e2%80%93-part-5-navigation-and-blocks/comment-page-1/#comment-1017</link>
		<dc:creator>craig</dc:creator>
		<pubDate>Mon, 03 Aug 2009 07:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://steven.macintyre.name/?p=2788#comment-1017</guid>
		<description>@kayani, By having each Block setup correctly in the blocks folder of the module, it should not be needed to define which module the block belongs to, as each classname should be unique, the sytem will look through each module till it finds the correct block,and instantiates that class, however, should you find that adding the module name to the table increases the performance or makes the system more expandable please let us know.</description>
		<content:encoded><![CDATA[<p>@kayani, By having each Block setup correctly in the blocks folder of the module, it should not be needed to define which module the block belongs to, as each classname should be unique, the sytem will look through each module till it finds the correct block,and instantiates that class, however, should you find that adding the module name to the table increases the performance or makes the system more expandable please let us know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kayani</title>
		<link>http://steven.macintyre.name/building-a-zend-modular-cms-system-%e2%80%93-part-5-navigation-and-blocks/comment-page-1/#comment-1008</link>
		<dc:creator>kayani</dc:creator>
		<pubDate>Sat, 01 Aug 2009 00:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://steven.macintyre.name/?p=2788#comment-1008</guid>
		<description>Great tutorial. I really like your idea for blocks. I was thinking of how to implement the db schema for this, yours seems just right. I might add an extra field to the table &#039;blocks&#039;   maybe something along the lines of  [module VARCHAR(100) NOT NULL default &#039;defaultmodulename&#039;]  to add module specific rendering of these blocks. so when we iterate over blocks of a position we also ensure they are supposed to be displayed for the current module.</description>
		<content:encoded><![CDATA[<p>Great tutorial. I really like your idea for blocks. I was thinking of how to implement the db schema for this, yours seems just right. I might add an extra field to the table &#8216;blocks&#8217;   maybe something along the lines of  [module VARCHAR(100) NOT NULL default 'defaultmodulename']  to add module specific rendering of these blocks. so when we iterate over blocks of a position we also ensure they are supposed to be displayed for the current module.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
