Hopefully I don't get flamed for saying this... but "anders" has a point. The senior contributors to this group already understand Cake, possibly even contributing to the development of Cake or writing articles on it. Thank you for your contributions!
That being said, there is a lot of misleading and conflicting information about Cake out there. It takes hours to research a topic (like how to use ExtJS with Cake) and then filter through the results to make sure it is Cake 1.2 compatible and the code suggested actually works. Often it does not, as comments to the posts frequently point out. Yes, the API is a great resource as is the "book." When reading those docs it helps to already understand some things about Cake. For newcomers to Cake, perhaps coming to Cake with a lot of experience in procedural languages but not OO languages, it is a daunting task to learn what the official docs are explaining. Add to this that not everyone learns the same way. It is a simple fact that educators have begun to recognize over the last 10 to 15 years. Different styles of learning need to accommodated. That's why there are books, tutorials, articles, samples, even video tutorials now. "[Write] some of your own stuff…" is good advice to contribute back to the Cake community. However it is a 'chicken and egg' scenario. When you read reviews about the available Cake books, there are some comments that are quite critical indicating that the code in the book is not correct. That's not good. I've found the style of the books from Packt Publishing to be helpful to my style of learning. Their book "CakePHP Application Development" presents theory first, what we are going to do with it, the code, then a section "What just happened?" That fits the classic model for teaching: tell them what you are going to tell them, tell them, then tell them what you told them. Ancient principle but it works. After reading a book, plus countless hours researching and filtering information from tutorials, I've found I tend to approach vague awareness and then I am more equipped to understand what I read in the API or official docs. What was the catch line for X Files? "The truth is out there." Be patient "anders" and you will slowly start to increase your fund of knowledge about Cake. On Aug 17, 10:58 am, thatsgreat2345 <[email protected]> wrote: > Read the API, don't like the docs? Right some of your own stuff if you > believe you can present it clearer. But the API and Book are very nice > and show everything that is needed. > > On Aug 17, 6:29 am, anders als <[email protected]> wrote: > > > hi there, > > > i like cake but my problem is finding ressources from which i can > > learn. > > > The cake manual does not provide every data i need, and often i have > > to test something 1000 times after shutting down my computer going > > outside and yelling "****** it does not work". > > > The problem is not the amount of information, it is the way how > > information were present in the manual. > > I look for code snippets and examples which aren't that much complex > > AND which are up2date (1.2 - 1.3). > > > My next point is, that i can not find any book which is about cakephp > > and is not older than 1 1/2 years :( > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
