<?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"
	>
<channel>
	<title>Comments on: One Application Down: Some Zend Framework Thoughts</title>
	<atom:link href="http://akrabat.com/2006/09/07/one-application-down-some-zend-framework-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://akrabat.com/2006/09/07/one-application-down-some-zend-framework-thoughts/</link>
	<description>Developing PHP and XUL Software in the Real World</description>
	<pubDate>Thu, 21 Aug 2008 22:56:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Taco Jung</title>
		<link>http://akrabat.com/2006/09/07/one-application-down-some-zend-framework-thoughts/#comment-5260</link>
		<dc:creator>Taco Jung</dc:creator>
		<pubDate>Sun, 10 Sep 2006 06:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.akrabat.com/2006/09/07/one-application-down-some-zend-framework-thoughts/#comment-5260</guid>
		<description>Could you give some more insight (detailed background info) on the what and how (functionality of AkCom_Controller_Action) of naming conventions for templates and lay-outs?!

As my projects are growing rapidly I'm struggling with the increasing number of templates/layouts/controllers/views and as the Zend Framework doesn't fully support sub-directories I'm interested in every possible solution for keeping things organised....</description>
		<content:encoded><![CDATA[<p>Could you give some more insight (detailed background info) on the what and how (functionality of AkCom_Controller_Action) of naming conventions for templates and lay-outs?!</p>
<p>As my projects are growing rapidly I'm struggling with the increasing number of templates/layouts/controllers/views and as the Zend Framework doesn't fully support sub-directories I'm interested in every possible solution for keeping things organised&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
