<?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: Early Impressions of CakePHP</title>
	<atom:link href="http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/</link>
	<description>presented by Site Potion</description>
	<pubDate>Mon, 06 Oct 2008 19:56:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: kristofer</title>
		<link>http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36732</link>
		<dc:creator>kristofer</dc:creator>
		<pubDate>Thu, 05 Jul 2007 13:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36732</guid>
		<description>:-D I'm glad you like it..

Scaffolding isn't really for production environments. It's just a place to start from.

I don't know if you're familiar with test-driven development or not, but you might be interested in http://simpletest.sourceforge.net

It's a development approach where defining the application behavior (with a test) comes before writing the actual behavior itself. http://behaviour-driven.org/ (this site is geared toward rails developers, but it applies)

It seems like changing the development style would only complicate things for myself and my clients, but I've found that by using test driven development I have less problems at crunch-time..</description>
		<content:encoded><![CDATA[<p> <img src='http://www.indywebshop.com/bestpractices/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' /> I&#8217;m glad you like it..</p>
<p>Scaffolding isn&#8217;t really for production environments. It&#8217;s just a place to start from.</p>
<p>I don&#8217;t know if you&#8217;re familiar with test-driven development or not, but you might be interested in <a href="http://simpletest.sourceforge.net" rel="nofollow">http://simpletest.sourceforge.net</a></p>
<p>It&#8217;s a development approach where defining the application behavior (with a test) comes before writing the actual behavior itself. <a href="http://behaviour-driven.org/" rel="nofollow">http://behaviour-driven.org/</a> (this site is geared toward rails developers, but it applies)</p>
<p>It seems like changing the development style would only complicate things for myself and my clients, but I&#8217;ve found that by using test driven development I have less problems at crunch-time..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clay</title>
		<link>http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36730</link>
		<dc:creator>Clay</dc:creator>
		<pubDate>Tue, 26 Jun 2007 12:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36730</guid>
		<description>I have played around a little with bake now.  It's impressive that they came up with such a comprehensive script to handle all the possible data associations.  I must be one of the few people that isn't at all tempted to use it for a production environment, though.  (The automatic input forms treat foreign keys as a select box with all the possible values of the foreign key, instead of a meaningful label?  There's just too many things like that.)  I anticipate I will use bake to create the model and control framework of my applications, but I probably won't even bother with creating the scaffolding views.

Thanks for putting me onto this framework, though, Kris.</description>
		<content:encoded><![CDATA[<p>I have played around a little with bake now.  It&#8217;s impressive that they came up with such a comprehensive script to handle all the possible data associations.  I must be one of the few people that isn&#8217;t at all tempted to use it for a production environment, though.  (The automatic input forms treat foreign keys as a select box with all the possible values of the foreign key, instead of a meaningful label?  There&#8217;s just too many things like that.)  I anticipate I will use bake to create the model and control framework of my applications, but I probably won&#8217;t even bother with creating the scaffolding views.</p>
<p>Thanks for putting me onto this framework, though, Kris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristofer</title>
		<link>http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36731</link>
		<dc:creator>Kristofer</dc:creator>
		<pubDate>Mon, 25 Jun 2007 15:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.indywebshop.com/bestpractices/2007/06/13/early-impressions-of-cakephp/#comment-36731</guid>
		<description>So you're enjoying your cakephp experience :-D

If you check out the 1.2 source there's a lot of killer new features like access control lists, and hopefully the return of data models as objects instead of associative arrays (this hasn't been implemented yet).

Bake is pretty cool. You can define you database according to the conventions defined in the manual and bake your applications with scaffolding and add things like admin routing and such to get a skeleton of the app. It's bittersweet though. You'll tend to think you can use scaffolding in your production applications, but it's not very good practice.

http://cakephp.org/screencasts/view/1 - a screencast demonstrating the way bake is used.

It's easy enough to convert existing apps to cake as well. It's possible to override the primary key and how relationships are defined by setting the model data appropriately. Nice article though!</description>
		<content:encoded><![CDATA[<p>So you&#8217;re enjoying your cakephp experience <img src='http://www.indywebshop.com/bestpractices/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' /><br />
If you check out the 1.2 source there&#8217;s a lot of killer new features like access control lists, and hopefully the return of data models as objects instead of associative arrays (this hasn&#8217;t been implemented yet).</p>
<p>Bake is pretty cool. You can define you database according to the conventions defined in the manual and bake your applications with scaffolding and add things like admin routing and such to get a skeleton of the app. It&#8217;s bittersweet though. You&#8217;ll tend to think you can use scaffolding in your production applications, but it&#8217;s not very good practice.</p>
<p><a href="http://cakephp.org/screencasts/view/1" rel="nofollow">http://cakephp.org/screencasts/view/1</a> - a screencast demonstrating the way bake is used.</p>
<p>It&#8217;s easy enough to convert existing apps to cake as well. It&#8217;s possible to override the primary key and how relationships are defined by setting the model data appropriately. Nice article though!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
