<?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: Current Zend View Path Helper</title>
	<atom:link href="http://www.gsdesign.ro/blog/current-zend-view-path-helper/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gsdesign.ro/blog/current-zend-view-path-helper/</link>
	<description>Just another developer blog</description>
	<lastBuildDate>Wed, 10 Mar 2010 20:57:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gabi Solomon</title>
		<link>http://www.gsdesign.ro/blog/current-zend-view-path-helper/comment-page-1/#comment-7430</link>
		<dc:creator>Gabi Solomon</dc:creator>
		<pubDate>Sun, 29 Mar 2009 19:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=372#comment-7430</guid>
		<description>Thanks for the tip,
I knew that you can extend them and use them afterward but didnt new how to replace the View in all the places that its used especially since i use Zend_Layout with MVC enebled.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip,<br />
I knew that you can extend them and use them afterward but didnt new how to replace the View in all the places that its used especially since i use Zend_Layout with MVC enebled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Weier O'Phinney</title>
		<link>http://www.gsdesign.ro/blog/current-zend-view-path-helper/comment-page-1/#comment-7429</link>
		<dc:creator>Matthew Weier O'Phinney</dc:creator>
		<pubDate>Sun, 29 Mar 2009 17:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=372#comment-7429</guid>
		<description>Basically every component of ZF&#039;s MVC may be replaced. In the case of the view, the easiest way is to inject it into the ViewRenderer in your bootstrap:

$view = new My_View();
$viewRenderer = Zend_Controller_Action_HelperBroker::getStaticHelper(&#039;ViewRenderer&#039;);
$viewRenderer-&gt;setView($view);

Once you&#039;ve done that, you&#039;re good to go.</description>
		<content:encoded><![CDATA[<p>Basically every component of ZF&#8217;s MVC may be replaced. In the case of the view, the easiest way is to inject it into the ViewRenderer in your bootstrap:</p>
<p>$view = new My_View();<br />
$viewRenderer = Zend_Controller_Action_HelperBroker::getStaticHelper(&#8216;ViewRenderer&#8217;);<br />
$viewRenderer-&gt;setView($view);</p>
<p>Once you&#8217;ve done that, you&#8217;re good to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabi Solomon</title>
		<link>http://www.gsdesign.ro/blog/current-zend-view-path-helper/comment-page-1/#comment-7428</link>
		<dc:creator>Gabi Solomon</dc:creator>
		<pubDate>Sun, 29 Mar 2009 14:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=372#comment-7428</guid>
		<description>@Matthew
The way i wanted to do it is to have the base path as a full path ( /home/user/applications/view/scripts ) and in my views i render scripts by givig them the path within that path ... /dir1/dir2/script.phtml and as i saw in the view abstract this gets concatenated and you will get the full path.

I might be wrong but having just a few ScriptPaths will make the view have fewer checks to find the full path.

As for the extending part, you are absolutely correct, but i didnt knew how to extend the View and also tell the Framework to use this view instead of the Original Zend_View.</description>
		<content:encoded><![CDATA[<p>@Matthew<br />
The way i wanted to do it is to have the base path as a full path ( /home/user/applications/view/scripts ) and in my views i render scripts by givig them the path within that path &#8230; /dir1/dir2/script.phtml and as i saw in the view abstract this gets concatenated and you will get the full path.</p>
<p>I might be wrong but having just a few ScriptPaths will make the view have fewer checks to find the full path.</p>
<p>As for the extending part, you are absolutely correct, but i didnt knew how to extend the View and also tell the Framework to use this view instead of the Original Zend_View.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Weier O'Phinney</title>
		<link>http://www.gsdesign.ro/blog/current-zend-view-path-helper/comment-page-1/#comment-7427</link>
		<dc:creator>Matthew Weier O'Phinney</dc:creator>
		<pubDate>Sun, 29 Mar 2009 13:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=372#comment-7427</guid>
		<description>A couple notes on this. First, using the full path relative to a view script directory is a better practice, as it encourages you to consider the relative domain of the view scripts you are consuming. If you want to shortcut this, add the current directory to your view script paths from within your view script or your controller:
$this-&gt;addScriptPath(dirname(__FILE__)); // within view script

Second, don&#039;t modify Zend_View_Abstract. Use proper OOP practices and extend Zend_View instead. ;)</description>
		<content:encoded><![CDATA[<p>A couple notes on this. First, using the full path relative to a view script directory is a better practice, as it encourages you to consider the relative domain of the view scripts you are consuming. If you want to shortcut this, add the current directory to your view script paths from within your view script or your controller:<br />
$this-&gt;addScriptPath(dirname(__FILE__)); // within view script</p>
<p>Second, don&#8217;t modify Zend_View_Abstract. Use proper OOP practices and extend Zend_View instead. <img src='http://www.gsdesign.ro/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
