<?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: First look at CakePHP</title>
	<atom:link href="http://www.askaboutphp.com/29/first-look-at-cakephp.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html</link>
	<description></description>
	<lastBuildDate>Wed, 10 Mar 2010 16:15:13 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gukan</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-8493</link>
		<dc:creator>Gukan</dc:creator>
		<pubDate>Wed, 22 Apr 2009 10:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-8493</guid>
		<description>any one help to me for install cakephp</description>
		<content:encoded><![CDATA[<p>any one help to me for install cakephp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: protospike</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-462</link>
		<dc:creator>protospike</dc:creator>
		<pubDate>Fri, 11 Jul 2008 20:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-462</guid>
		<description>I would tend to agree with you that beginners should not use a framework until doing some &quot;hand-tooled&quot; OOP, in whatever language. Frameworks are at a pretty high level of abstraction and without understanding the lower level stuff (the basic OOP concepts), it&#039;s kind of difficult to know what&#039;s happening in the framework.

Also here&#039;s a tip. The difference between a library and a framework is this:

YOU call the library.
The framework calls YOU.</description>
		<content:encoded><![CDATA[<p>I would tend to agree with you that beginners should not use a framework until doing some &#8220;hand-tooled&#8221; OOP, in whatever language. Frameworks are at a pretty high level of abstraction and without understanding the lower level stuff (the basic OOP concepts), it&#8217;s kind of difficult to know what&#8217;s happening in the framework.</p>
<p>Also here&#8217;s a tip. The difference between a library and a framework is this:</p>
<p>YOU call the library.<br />
The framework calls YOU.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Poncho</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-77</link>
		<dc:creator>Poncho</dc:creator>
		<pubDate>Fri, 09 May 2008 11:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-77</guid>
		<description>Good to see CakePHP getting some love. I&#039;ve been building pretty complex apps with cake for a couple of years and it certainly does make life easier for the developer.

I agree that it would be best to learn a framework after becoming comfortable with OOP programming in general, as well as completing a few applications.

I myself had got to the stage of using DB libraries, class-table relationships and template engines (without realising I was using the MVC pattern) before I discovered CakePHP, so it came pretty naturally to me.

CakePHP offers some pretty advanced features with a minimum of effort including; incredible URL routing, easy database relationships, full data sanitisation &amp; validation, plenty of useful components (Security, Session, Cookie, Request, Auth, Email) and view helpers (html, form, session, etc.).

I won&#039;t even go into the command-line tools, I will just say that they are incredible powerful.

After trying out a lot of CMS and frameworks, I found CakePHP offers an awful lot of value for the little structure it imposes (such structure is both useful and &#039;guessable&#039;).

Cheers;
Poncho</description>
		<content:encoded><![CDATA[<p>Good to see CakePHP getting some love. I&#8217;ve been building pretty complex apps with cake for a couple of years and it certainly does make life easier for the developer.</p>
<p>I agree that it would be best to learn a framework after becoming comfortable with OOP programming in general, as well as completing a few applications.</p>
<p>I myself had got to the stage of using DB libraries, class-table relationships and template engines (without realising I was using the MVC pattern) before I discovered CakePHP, so it came pretty naturally to me.</p>
<p>CakePHP offers some pretty advanced features with a minimum of effort including; incredible URL routing, easy database relationships, full data sanitisation &amp; validation, plenty of useful components (Security, Session, Cookie, Request, Auth, Email) and view helpers (html, form, session, etc.).</p>
<p>I won&#8217;t even go into the command-line tools, I will just say that they are incredible powerful.</p>
<p>After trying out a lot of CMS and frameworks, I found CakePHP offers an awful lot of value for the little structure it imposes (such structure is both useful and &#8216;guessable&#8217;).</p>
<p>Cheers;<br />
Poncho</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJfiers</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-59</link>
		<dc:creator>PJfiers</dc:creator>
		<pubDate>Thu, 08 May 2008 14:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-59</guid>
		<description>Aye, I agree with Waggoner here.

I&#039;ve taken a few programming courses, mainly to get that sheet of paper to show I can (or should be able) to program. What I found to be the worst in every course i&#039;ve taken on programming is that OOP is regarded too advanced.

I say it&#039;s such a integral part of building good applications it should be fed with the spoon as early as possible. They way its done now is like teaching someone how to the chacha before teaching them about rythm and such. 

The problem however, is that cakePHP will be hard to grasp without any knowledge of OOP. First someone should learn to build a little framework himself, very basic before jumping on a vast frame work as this.</description>
		<content:encoded><![CDATA[<p>Aye, I agree with Waggoner here.</p>
<p>I&#8217;ve taken a few programming courses, mainly to get that sheet of paper to show I can (or should be able) to program. What I found to be the worst in every course i&#8217;ve taken on programming is that OOP is regarded too advanced.</p>
<p>I say it&#8217;s such a integral part of building good applications it should be fed with the spoon as early as possible. They way its done now is like teaching someone how to the chacha before teaching them about rythm and such. </p>
<p>The problem however, is that cakePHP will be hard to grasp without any knowledge of OOP. First someone should learn to build a little framework himself, very basic before jumping on a vast frame work as this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskAboutPHP.com: First look at CakePHP &#124; Development Blog With Code Updates : Developercast.com</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-43</link>
		<dc:creator>AskAboutPHP.com: First look at CakePHP &#124; Development Blog With Code Updates : Developercast.com</dc:creator>
		<pubDate>Wed, 07 May 2008 19:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-43</guid>
		<description>[...] a recent post to the Ask About PHP blog, there&#8217;s a quick &#8220;first look&#8221; at the CakePHP framework [...]</description>
		<content:encoded><![CDATA[<p>[...] a recent post to the Ask About PHP blog, there&#8217;s a quick &#8220;first look&#8221; at the CakePHP framework [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Waggoner</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-42</link>
		<dc:creator>Ryan Waggoner</dc:creator>
		<pubDate>Wed, 07 May 2008 18:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-42</guid>
		<description>Great post, and I agree with everything you&#039;ve said except that beginners shouldn&#039;t start with CakePHP or a framework of some kind.  While it definitely adds a layer of complexity and will be harder to learn initially than just straight PHP, hopefully that will avoid that coder learning some really bad habits that may be hard to break later on.  

In the worst cases, I&#039;ve seen PHP developers who were so entrenched in their awful coding habits that they refused to go through the added hassle of learning a framework later on.

The fact that you can just jump in and use PHP for whatever is a great strength, but also a great weakness.  I really wish that I had started with a framework or two so that I could have learned the right way to do things rather than the easy way.  It would have saved me a lot of time in the long run and made me a much better developer.

Keep up the good work!</description>
		<content:encoded><![CDATA[<p>Great post, and I agree with everything you&#8217;ve said except that beginners shouldn&#8217;t start with CakePHP or a framework of some kind.  While it definitely adds a layer of complexity and will be harder to learn initially than just straight PHP, hopefully that will avoid that coder learning some really bad habits that may be hard to break later on.  </p>
<p>In the worst cases, I&#8217;ve seen PHP developers who were so entrenched in their awful coding habits that they refused to go through the added hassle of learning a framework later on.</p>
<p>The fact that you can just jump in and use PHP for whatever is a great strength, but also a great weakness.  I really wish that I had started with a framework or two so that I could have learned the right way to do things rather than the easy way.  It would have saved me a lot of time in the long run and made me a much better developer.</p>
<p>Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smily</title>
		<link>http://www.askaboutphp.com/29/first-look-at-cakephp.html/comment-page-1#comment-35</link>
		<dc:creator>smily</dc:creator>
		<pubDate>Tue, 06 May 2008 03:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.askaboutphp.com/?p=29#comment-35</guid>
		<description>Heh I can identify with that stage you described where I&#039;ve written a few major things and now I want to start doing things the proper way because i&#039;m pretty sure whoever&#039;s going to inherit my old code will hate me! If you like cakePHP you might like kohana/code igniter which I&#039;ve been playing with too.</description>
		<content:encoded><![CDATA[<p>Heh I can identify with that stage you described where I&#8217;ve written a few major things and now I want to start doing things the proper way because i&#8217;m pretty sure whoever&#8217;s going to inherit my old code will hate me! If you like cakePHP you might like kohana/code igniter which I&#8217;ve been playing with too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
