<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Designing for Reusability: Taking advantage of Plugins in CakePHP</title>
	<link>http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-taking-advantage-of-plugins-in-cakephp/</link>
	<description>News, Developments and Best practices for programming</description>
	<pubDate>Fri, 04 Jul 2008 23:30:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: admin</title>
		<link>http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-taking-advantage-of-plugins-in-cakephp/#comment-180</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 19 Apr 2008 04:16:44 +0000</pubDate>
		<guid>http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-taking-advantage-of-plugins-in-cakephp/#comment-180</guid>
		<description>Yea, I admit it involves use of hacks, but there is no proper way right to communicate with plugin well.

So, when doing your own reusable part of code, you have to do some custom hacks yourself rather than waiting for it. However, I'll be interested in seeing how the rest of Cake community takes this idea and solves the problem.

Most important features to cover up in plugin are:

1. Plugin Callbacks like beforeFilter(), afterFilter()

2. Serving images for plugins. (It supports CSS and JS already).

3. Some focus on inter-plugin communication.

When something like this is done, you can start seeing your app from big picture, and you would never have to reinvent the wheel.</description>
		<content:encoded><![CDATA[<p>Yea, I admit it involves use of hacks, but there is no proper way right to communicate with plugin well.</p>
<p>So, when doing your own reusable part of code, you have to do some custom hacks yourself rather than waiting for it. However, I&#8217;ll be interested in seeing how the rest of Cake community takes this idea and solves the problem.</p>
<p>Most important features to cover up in plugin are:</p>
<p>1. Plugin Callbacks like beforeFilter(), afterFilter()</p>
<p>2. Serving images for plugins. (It supports CSS and JS already).</p>
<p>3. Some focus on inter-plugin communication.</p>
<p>When something like this is done, you can start seeing your app from big picture, and you would never have to reinvent the wheel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-taking-advantage-of-plugins-in-cakephp/#comment-178</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Sat, 19 Apr 2008 03:42:56 +0000</pubDate>
		<guid>http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-taking-advantage-of-plugins-in-cakephp/#comment-178</guid>
		<description>Even though this article focuses on plugins, but doing custom hacks through out your applications might not be the best way. Its kinda interesting approach however.</description>
		<content:encoded><![CDATA[<p>Even though this article focuses on plugins, but doing custom hacks through out your applications might not be the best way. Its kinda interesting approach however.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
