<?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: CakePHP DebugKit: Take Back your Debugging</title>
	<atom:link href="http://blog.japanesetesting.com/2009/11/12/cakephp-debugkit-take-back-your-debugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.japanesetesting.com/2009/11/12/cakephp-debugkit-take-back-your-debugging/</link>
	<description>Design and Programming of a mISV Site</description>
	<lastBuildDate>Fri, 23 Jul 2010 13:29:41 +0900</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Widgity! Multi-element designs with CakePHP &#187; Adventures in Japanese Programming</title>
		<link>http://blog.japanesetesting.com/2009/11/12/cakephp-debugkit-take-back-your-debugging/comment-page-1/#comment-229</link>
		<dc:creator>Widgity! Multi-element designs with CakePHP &#187; Adventures in Japanese Programming</dc:creator>
		<pubDate>Tue, 27 Apr 2010 09:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.japanesetesting.com/?p=115#comment-229</guid>
		<description>[...] On my site, each of the widgets is a separate element, and the way I used to deal with deciding which page to display them on was by running a RequestAction on my Widgets Controller, which in turn grabbed the widget data from the DB, checked which widgets needed to be displayed when, grabbed the elements, and then displayed each of them. Overall a very thorough way of managing and displaying the widgets, but not very nice on my load-time (especially when I started using DebugKit). [...]</description>
		<content:encoded><![CDATA[<p>[...] On my site, each of the widgets is a separate element, and the way I used to deal with deciding which page to display them on was by running a RequestAction on my Widgets Controller, which in turn grabbed the widget data from the DB, checked which widgets needed to be displayed when, grabbed the elements, and then displayed each of them. Overall a very thorough way of managing and displaying the widgets, but not very nice on my load-time (especially when I started using DebugKit). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
