Re: CakePHP guide
Why do we keep comparing to Zend? They got an entire team on doc. alone. The think that our only problem here lies with 1.2. IMO, the current 1.1manual is fine for me (maybe have one complete doc, so you don't have to keep clicking through chapters). The only thing we need right now is to get the 1.2 functionality up to that level. But the only thing I would blatantly plagiarize from Zend is the list of examples at the bottom. On Feb 8, 2008 11:08 AM, Mech7 [EMAIL PROTECTED] wrote: Hmmm yes all these blogs scattered everywhere really doesn't help anybody... I hope one day cake will have a manual to the standards of ZendFW.. http://framework.zend.com/manual/en/ It's easy to read and has lots of example code... for every part of the framework. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hmmm yes all these blogs scattered everywhere really doesn't help anybody... I hope one day cake will have a manual to the standards of ZendFW.. http://framework.zend.com/manual/en/ It's easy to read and has lots of example code... for every part of the framework. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I quite like the system in php.net - you've got the official docs pages, then a list of user-submitted relevant comments underneath. I often find what I'm looking for in the user comments. If these could be moderated and other users could vote on them, it might make for a fine system to add to the cakephp docs. On Feb 8, 5:19 pm, Baz [EMAIL PROTECTED] wrote: Why do we keep comparing to Zend? They got an entire team on doc. alone. The think that our only problem here lies with 1.2. IMO, the current 1.1manual is fine for me (maybe have one complete doc, so you don't have to keep clicking through chapters). The only thing we need right now is to get the 1.2 functionality up to that level. But the only thing I would blatantly plagiarize from Zend is the list of examples at the bottom. On Feb 8, 2008 11:08 AM, Mech7 [EMAIL PROTECTED] wrote: Hmmm yes all these blogs scattered everywhere really doesn't help anybody... I hope one day cake will have a manual to the standards of ZendFW..http://framework.zend.com/manual/en/ It's easy to read and has lots of example code... for every part of the framework. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I second this. it's a great way to provide the general method and usage while also providing multiple, more specific examples that often are more relevant in the real world. brian Quoting grigri [EMAIL PROTECTED]: I quite like the system in php.net - you've got the official docs pages, then a list of user-submitted relevant comments underneath. I often find what I'm looking for in the user comments. If these could be moderated and other users could vote on them, it might make for a fine system to add to the cakephp docs. On Feb 8, 5:19 pm, Baz [EMAIL PROTECTED] wrote: Why do we keep comparing to Zend? They got an entire team on doc. alone. The think that our only problem here lies with 1.2. IMO, the current 1.1manual is fine for me (maybe have one complete doc, so you don't have to keep clicking through chapters). The only thing we need right now is to get the 1.2 functionality up to that level. But the only thing I would blatantly plagiarize from Zend is the list of examples at the bottom. On Feb 8, 2008 11:08 AM, Mech7 [EMAIL PROTECTED] wrote: Hmmm yes all these blogs scattered everywhere really doesn't help anybody... I hope one day cake will have a manual to the standards of ZendFW..http://framework.zend.com/manual/en/ It's easy to read and has lots of example code... for every part of the framework. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I quite like the system in php.net - you've got the official docs pages, then a list of user-submitted relevant comments underneath. I often find what I'm looking for in the user comments. If these could be moderated and other users could vote on them, it might make for a fine system to add to the cakephp docs. look at the unofficial effort at http://docs.cakephp.nu/ -- -- (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/ http://blog.samdevore.com/cakephp-pages/my-cake-wont-bake/ http://blog.samdevore.com/cakephp-pages/i-cant-bake/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Isn't that just like the API, generated from code? And it seems to have stopped after 11/7/07 On Feb 8, 2008 2:54 PM, Samuel DeVore [EMAIL PROTECTED] wrote: I quite like the system in php.net - you've got the official docs pages, then a list of user-submitted relevant comments underneath. I often find what I'm looking for in the user comments. If these could be moderated and other users could vote on them, it might make for a fine system to add to the cakephp docs. look at the unofficial effort at http://docs.cakephp.nu/ -- -- (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/ http://blog.samdevore.com/cakephp-pages/my-cake-wont-bake/ http://blog.samdevore.com/cakephp-pages/i-cant-bake/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
[EMAIL PROTECTED] wrote: I second this. it's a great way to provide the general method and usage while also providing multiple, more specific examples that often are more relevant in the real world. ONLY if they are moderated... too many people use the comments as a place to request free help, and then the doc's degenerate quickly. That and a lot of inaccurate or incomplete information getting posted. I like the idea, but someone's gotta ride herd on it. -Scott Quoting grigri [EMAIL PROTECTED]: I quite like the system in php.net - you've got the official docs pages, then a list of user-submitted relevant comments underneath. I often find what I'm looking for in the user comments. If these could be moderated and other users could vote on them, it might make for a fine system to add to the cakephp docs. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 8, 2008 2:10 PM, Baz [EMAIL PROTECTED] wrote: Isn't that just like the API, generated from code? And it seems to have stopped after 11/7/07 I think the plan was that it was going to support the notion of comments like the php.net manual. But like you said it died, which has been the history of non-official documentation. Here is my opinion on the docs, if you need something written or want to right something for it look at the list of needs and right it and just send it to John, he will make it look right and sound right and you will feel good. Or he will send it back and let you know what to fix/ add -- -- (the old fart) the advice is free, the lack of crankiness will cost you - its a fine line between a real question and an idiot http://blog.samdevore.com/archives/2007/03/05/when-open-source-bugs-me/ http://blog.samdevore.com/cakephp-pages/my-cake-wont-bake/ http://blog.samdevore.com/cakephp-pages/i-cant-bake/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I would like to offer some help with the official docs. I'm not sure how much time i can put in because, like everyone else, i've got a crap-load on my plate already. But the docs do need some serious help. The presentation, for one, makes it difficult to find things. That, and the underlying generated markup is horrendous. John: i don't at all mean to criticise; i fully understand the situation. I'm just pointing out a couple of areas that i think could use some improvement, since this thread is beginning to look like a sign-up sheet. Zoe: your guide is a huge addition! Maybe it can be folded into the official docs, or maybe it can become a companion guide. Perhaps some agreement about that can be reached, and might spur both projects forward. I agree with Baz Zoe about not quite knowing whether the steps i'm taking are appropriate. With the new behaviors and whatnot, coupled with all of the novel ways people are coming up with to do things, it can be a bit dizzying trying to figure out just what is appropriate. Just yesterday, i spent ages going over Andy's Attachment behavior, trying to make sense of the (almost) comment-less code. The good thing is that I learned a great deal about Cake (and a couple of neat PHP tricks). And I realised that my brainwave to deal with uploads in the validation code was ... validated by others--more astute about Cake than I--who'd figured it out already. The best, though, was that, after finally judging that I had Andy's behavior figured out, I stumbled upon David Persson's wonderful (and wonderfully-packaged) Attachments Project[1], built upon a collection of others' cool ideas (including Andy's). Going through the source I suddenly had botha revelation for how Cake works (or, at least, should) and inspiration for how to resolve some long-standing problems with my project (well over and above those things that Cake has already addressed for me). My point being that good documentation--especially in the source--can help tremendously. [1] http://cakeforge.org/projects/attm/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hello Zoe, Thank you for your great work. I am using cakePHP reading the source code. So, Now I can use cakePHP as I want in many cases. However we need the guide for beginners, and I think your guide will be such guide. By the way, I am Japanese. I think Japanese developers want to read documents in Japanese. So I want to translate your guide into Japanese. Can I do that? Best Wishes, Takuo Shiono MonkeyGirl wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hi verybody! I'm really newbie with Cake (since 4 months) and I'm French... Of course, doc is a negative point for Cake, compared with Symfony or Zend (and notably for international users they don't read English easily). It's harder to find, it's not updated, it's not simple. But I'm agree with Nate and John : why all documentation efforts aren't put towards the official documentation? why people criticise instead of contribute? Maybe the way to contribute and doc presentation are not very clear. For example, the tempdoc for 1.2 beta is not practical to read : a long scroll, with blanks in some parts... and nothing to announce updates, so we must always scroll to find if new things are added. The Bakery is a good idea, but its organisation is not clear and not enough efficient. The structure of information is not logical, not progressive. This is a catch-all... Of course, CakePHP is work in progress and the 1.2 is on beta version. Like John said: create a stable documentation for a beta software is difficult! Zoe, your initiative is good, John and Nate, your opinions are right, so isn't possible to find a common ground and write an only official doc? And after that, French, Japanese, German, Spanish and many other Cakers can translate your prose! Sorry for my simple English... Avairet On Feb 3, 7:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Settle down - I think you've completely over-reacted. Nate's comment wasn't a flame, but yours was. While Nate's opinion might be correct here (up to a point), it is obvious that his people skills are not his forte.. This is not a flame, it is just an opinion. No hard feelings towards Nate, I still believe he's doing a great job; but if he's going to attract new community members with replies like (real quote) Dude, you're confusing some very unrelated things. and never elaborate his statement, there is a great chance people will just run away. Nobody likes to be treated like an idiot, not even real idiots. So there. My 2c. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 6, 5:03 pm, Baz [EMAIL PROTECTED] wrote: I'm never sure whether I'm doing things the right way. To be honest, all this MVC stuff was brand new to me by the time I started. This is why I've been hesitant to submit articles to the bakery, for example. Since a lot of my stuff, can be considered patchwork, I wouldn't want to mislead people searching for official solutions on the bakery (and even Official Docs). That's why I usually keep my ramblings on my own blog. This sums up how I feel as well. I dived into using CakePHP maybe a year ago now, and it's taken me all this time to get from the stage where it works, all the way to the stage where I'm starting to use it in the proper MVC spirit. I find it difficult working out from the API/source code just what's going on. For example, it takes me anything up to an hour sometimes just to work out how to do something like disable labels using the form helper, trying to work out where all the different option array elements are being used. So I want to help other people out, but I worry I'm not doing things the right way. On my own site, I can say this is how I'm making sites. It works, but it may not be the best way. Please tell me if you find a better way of doing something and I'll update my guide to do it that way instead. If I was writing official documentation, I'd feel like I was saying this is how it's *supposed* to be done, how it *should* be done. I don't feel confident enough to make that claim. If anyone else can get the documentation and code commenting to the stage where us early adopters of CakePHP 1.2 can see what each method of each class is doing in sufficient detail, I'm sure we can all group together and help with the official documentation. I'd be happy to, and it looks like others are too. Is this something we can do together? I hope I'm not out of line with these suggestions, I'm just trying to help bridge the gap between those who are great at writing code, and those like myself who are perhaps not so good at programming, but are still good at explaining how things work in simpler terms. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
By the way, I am Japanese. I think Japanese developers want to read documents in Japanese. So I want to translate your guide into Japanese. Can I do that? The way I understand the hacker spirit, everybody's free to share and build upon everyone else's work, which is what makes free software and the Internet so great. I can't speak for anyone else, but you're welcome to translate my guide into any language you'd like, and I'd be happy to host any translations of it. I'm guessing this is also the kind of help the official documentation also needs, and I agree that we should all be helping with that too. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Rajesh, The new application is very wiki-like. It allows easy contributions (hopefully). It's different in that it has more structure (data is in tree form) and there's an approval/revision process built in. We hope it'll make things easier - hopefully we can have something to show really soon. -- John On Feb 7, 2008, at 12:42 PM, Rajesh wrote: I ever think that you understood what i wrote. i just tried to explain what would ease the pressure on you guys. If there was a discussion previously on wiki, you could have just said NO for a wiki or Its on the way but not they way you had said. I just started cakePHP for about 4 months now and i don't or i can't read all the postings in this group. I just search if i wanted something.I just found out that there was a previous discussion on wiki and what _psychic_ had replied. Given the duration of my learning in cakephp, i will not be able to write pages of documentation at this point, but atleast i can help find/edit something that is not correct or that can be enhanced to my knowledge. On Feb 7, 1:58 pm, Chris Hartjes [EMAIL PROTECTED] wrote: On Feb 7, 2008 1:03 PM, Rajesh [EMAIL PROTECTED] wrote: Just a suggestion, why not open up a WIKI where everyone can contribute and have a set of people as Moderators, that way sending emails back and forth for documentation would reduce and also that would ease the load on the people writing the current documentation. -Rajesh Again with the same old tired refrain about the inexplicable need for a wiki. Does nobody read the emails that our overworked and underappreciated documentation expert _psychic_ puts out? Because in those emails he's talked several times about a wiki-like solution that is on the way. If you have your heart set on a wiki, then put one up yourself and tell the list about it. Given the level of participation in the current documentation project, I'd be surprised if you get anything of value posted. -- Chris Hartjes Internet Loudmouth Motto for 2008: Moving from herding elephants to handling snakes... @TheKeyBoard:http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Thanks John for the reply. I really look forward to the new wiki-like application. - Rajesh --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Just a suggestion, why not open up a WIKI where everyone can contribute and have a set of people as Moderators, that way sending emails back and forth for documentation would reduce and also that would ease the load on the people writing the current documentation. -Rajesh --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I like that one. On Feb 7, 2008 4:03 PM, Rajesh [EMAIL PROTECTED] wrote: Just a suggestion, why not open up a WIKI where everyone can contribute and have a set of people as Moderators, that way sending emails back and forth for documentation would reduce and also that would ease the load on the people writing the current documentation. -Rajesh --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 7, 2008, at 6:17 AM, MonkeyGirl wrote: snip find a better way of doing something and I'll update my guide to do it that way instead. If I was writing official documentation, I'd feel like I was saying this is how it's *supposed* to be done, how it *should* be done. I don't feel confident enough to make that claim. There's plenty of eyes that go on official docs before they go out the door. Helping the official docs effort doesn't mean we give you the keys and walk away. No one (especially at first) really has publishing power like that. It's a collaborative effort. Most people submitting docs just hand me what they have. I edit the submissions for (grammar, spelling) voice, style, etc but we also edit for completeness and correctness. Sometimes I'll hand it back with some suggestions, but I mostly try to iron out what I can in order to make the submission process easier. Being too new shouldn't be a problem, nor is a worry about accuracy. If anyone else can get the documentation and code commenting to the stage where us early adopters of CakePHP 1.2 can see what each method of each class is doing in sufficient detail, I'm sure we can all group together and help with the official documentation. I'd be happy to, and it looks like others are too. Experience shows that they aren't. Experience shows that I *can't* get someone else to do that. It wasn't that way with 1.1, at least. Forgive me for being frank, but no one likes to help in the docs. Most people prefer to either 1: complain without helping, or 2: publish things themselves. The problem with 1 is obvious, and the problem with 2 is that we're unfocused as a community. Why are people publishing their own rather than jumping in to an official effort? It's probably some combination of these: 1. The submission process isn't clear (my fault) 2. Docs are a moving target for beta software (my fault) 3. People enjoy the credit and traffic self-published material generates 4. The docs situation is too bad to be helped (my fault), or 5. The docs situation isn't as bad as people think. I'm about ready to try the experiment of quitting, mostly to see if I'm the bottleneck. Maybe that's the problem, I don't really know. It's hard to see how I'm really doing, because I don't feel like I've ever really had an abundance of support. In two years, there's only a handful of people that have contributed multiple times (that aren't already overwhelmed with core team responsibilities). In any case, this is really like waiting to take your medicine until you feel well. Why would we need documentation if everyone can see what each method of each class is doing in sufficient detail ? If we're doing that, I think we're nearly done. It's rather obvious we need help *now*. :) Is this something we can do together? I hope I'm not out of line with these suggestions, I'm just trying to help bridge the gap between those who are great at writing code, and those like myself who are perhaps not so good at programming, but are still good at explaining how things work in simpler terms. Right now I'm working on getting our new docs application online and ready for everyone. Everyone else is at Cakefest this week, so it's been hard to make decisions on things. Stay tuned, I'm working as best I can to solve these problems. I'm banking on the guess that this docs app will help out the docs process, so here's hoping. Thanks for the input, -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Ok ok ok, enough of all this talk Pointing fingers is going to help. I gather that people are busy, due to CakeFest etc. But when that's done, I'm expecting someone to send me a link or something telling me where to go to sign up for stuff. Because I've heard tons of complaints about nobody being willing to help with docs. I admit (for reasons previously stated) that I had my reservations. However, since it has been made abundantly clear that being new is NOT a problem, let's get this thing going. 1. Is there an existing system that you guys use or do I just start blabbing away? 2. Should I just focus on incomplete stuff in tempdocs or should I add to what I already know? 3. Can I add code? I personally find code examples EXTREMELY useful? 4. Assuming the API is generated off the code, can I maybe add examples to the doc blocks of some functions? $form anyone? 5. How does the Bakery fit into all of this? Will it be used for stuff not in the core? 6. Finally, just tell me where to sign up. Zoe, no offense intended, but I agree with John, someone needs to start working on the official docs, otherwise CakePHP will remain an underground framework. Just ask the folks who have tried to convince bosses and project managers to use CakePHP. I'm willing to help, point me in the right direction. -- Baz L Web Development 2.0 http://WebDevelopment2.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
That attitude is the exact difference between ExtJS which is more community-driven and Zend, which is cold and company-driven. ExtJS succeeds because the community-force behind it drives it forward, because people make tons of plugins. Because they don't need a bakery, they have a simple forum with a WORKING SEARCH. You should check how people are turning into staff/core contributers there and get a job if they're good enough. I didn't see anyone of the core-staff in there bitch about how stupid people are, how questions are being asked over and over again. Those messages made by users are either deleted or ignored. I think that only an idiot would be happy to contribute to anything after such a stupid comment. I like CakePHP as a product (otherwise I wouldn't be here), but nate, you should work on your human skills. On Feb 4, 6:48 pm, nate [EMAIL PROTECTED] wrote: The only comment or criticism I have is that it's a shame that such efforts aren't put towards the official documentation. John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I don't mean to denigrate your efforts here, but I really think that efforts like these often serve to scatter and spread the pool of useful information thinner, which just makes it harder to find, which makes people more frustrated. On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 6, 2008, at 9:25 AM, phpjoy wrote: That attitude is the exact difference between ExtJS which is more community-driven and Zend, which is cold and company-driven. ExtJS succeeds because the community-force behind it drives it forward, because people make tons of plugins. Because they don't need a bakery, they have a simple forum with a WORKING SEARCH. How exactly does a forum do what the Bakery does? What are you talking about? You should check how people are turning into staff/core contributers there and get a job if they're good enough. I didn't see anyone of the core-staff in there bitch about how stupid people are, how questions are being asked over and over again. Those messages made by users are either deleted or ignored. Um, from what I can tell, Nate was *not* complaining about anything besides the lack of unfocused documentation efforts. Please put your straw man away and read his message again. I think that only an idiot would be happy to contribute to anything after such a stupid comment. I like CakePHP as a product (otherwise I wouldn't be here), but nate, you should work on your human skills. Settle down - I think you've completely over-reacted. Nate's comment wasn't a flame, but yours was. -- John On Feb 4, 6:48 pm, nate [EMAIL PROTECTED] wrote: The only comment or criticism I have is that it's a shame that such efforts aren't put towards the official documentation. John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I don't mean to denigrate your efforts here, but I really think that efforts like these often serve to scatter and spread the pool of useful information thinner, which just makes it harder to find, which makes people more frustrated. On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 6, 2008 9:55 PM, phpjoy [EMAIL PROTECTED] wrote: I think that only an idiot would be happy to contribute to anything after such a stupid comment. I like CakePHP as a product (otherwise I wouldn't be here), but nate, you should work on your human skills. Huh! Where did that come from? T -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Personally, this is the problem I have with the lack of documentation: CakePHP was somewhat intimidating for me to get started with. With that said, I have done a few simple apps, an make-shift CMS that serves my purpose, and just general fudging around with stuff and trying to get things working. However, I'm never sure whether I'm doing things the right way. To be honest, all this MVC stuff was brand new to me by the time I started. This is why I've been hesitant to submit articles to the bakery, for example. Since a lot of my stuff, can be considered patchwork, I wouldn't want to mislead people searching for official solutions on the bakery (and even Official Docs). That's why I usually keep my ramblings on my own blog. I can't help but feel that I'm not the only one who feels that way. What would qualify one to be able to contribute to the Official Cake documentation or the Bakery? Just My 2 cents. PS: - The API is a great resource as is, but it can be HEAVILY improved by just placing a few (well a whole lot) of examples for some of the more difficult functions. $form-input() any one? I tend to get lost in the MANY uses of options arrays. - I've found some hidden treasures in: http://bin.cakephp.org/saved. The pagination on that page doesn't work though. I didn't find a category to report it under in trac. -- Baz L Web Development 2.0 http://WebDevelopment2.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 6, 2008, at 10:03 AM, Baz wrote: I can't help but feel that I'm not the only one who feels that way. What would qualify one to be able to contribute to the Official Cake documentation or the Bakery? There is no qualification. New people have the distinct advantage of being able to point out weaknesses. If nothing else, let us know what needs strength or better coverage. The Bakery probably isn't for noobs, but helping proof and suggest sections to the existing docs is extremely helpful to me. -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I completely agree with the comment about the API. I realize it is a very technical document with a specific purpose, but a few lines of example code here and there would broaden its reach to many more users. I also agree with the sentiment about wanting to contribute but being unsure of one's qualification to do so. I'd like to add things, or sometimes just expand and append parts of the manual, but the only way to do it easily is through your own blog. -Andrew On Feb 6, 12:03 pm, Baz [EMAIL PROTECTED] wrote: Personally, this is the problem I have with the lack of documentation: CakePHP was somewhat intimidating for me to get started with. With that said, I have done a few simple apps, an make-shift CMS that serves my purpose, and just general fudging around with stuff and trying to get things working. However, I'm never sure whether I'm doing things the right way. To be honest, all this MVC stuff was brand new to me by the time I started. This is why I've been hesitant to submit articles to the bakery, for example. Since a lot of my stuff, can be considered patchwork, I wouldn't want to mislead people searching for official solutions on the bakery (and even Official Docs). That's why I usually keep my ramblings on my own blog. I can't help but feel that I'm not the only one who feels that way. What would qualify one to be able to contribute to the Official Cake documentation or the Bakery? Just My 2 cents. PS: - The API is a great resource as is, but it can be HEAVILY improved by just placing a few (well a whole lot) of examples for some of the more difficult functions. $form-input() any one? I tend to get lost in the MANY uses of options arrays. - I've found some hidden treasures in:http://bin.cakephp.org/saved. The pagination on that page doesn't work though. I didn't find a category to report it under in trac. -- Baz L Web Development 2.0http://WebDevelopment2.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hey, awsome work Zoe :) The official docs is really missing something like this. As Mark said, a rails book like tutorial is a great idea too. The lack of good, consistent and updated documentation is the worst problem for new users. I agree with brian about the 'hidden' 1.2 docs. In the end every effort will be good for people learning cake. Be it already official, or new. It's very important use as many ways as possible to teach things, so we can touch as many minds as possible too. Learning and teaching needs to bee plural. Lets get the best ideas and make it official when its mature. -- Julio Vinicius Protzek --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
This is great! Thanks. -- Aaron On 5 Feb, 08:58, Julio Protzek [EMAIL PROTECTED] wrote: Hey, awsome work Zoe :) The official docs is really missing something like this. As Mark said, a rails book like tutorial is a great idea too. The lack of good, consistent and updated documentation is the worst problem for new users. I agree with brian about the 'hidden' 1.2 docs. In the end every effort will be good for people learning cake. Be it already official, or new. It's very important use as many ways as possible to teach things, so we can touch as many minds as possible too. Learning and teaching needs to bee plural. Lets get the best ideas and make it official when its mature. -- Julio Vinicius Protzek --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
theres a book coming for Cake too - by David Golding: http://www.amazon.com/Beginning-CakePHP-Professional-David-Golding/dp/1430209771/ On Feb 5, 10:11 am, accom06 [EMAIL PROTECTED] wrote: This is great! Thanks. -- Aaron On 5 Feb, 08:58, Julio Protzek [EMAIL PROTECTED] wrote: Hey, awsome work Zoe :) The official docs is really missing something like this. As Mark said, a rails book like tutorial is a great idea too. The lack of good, consistent and updated documentation is the worst problem for new users. I agree with brian about the 'hidden' 1.2 docs. In the end every effort will be good for people learning cake. Be it already official, or new. It's very important use as many ways as possible to teach things, so we can touch as many minds as possible too. Learning and teaching needs to bee plural. Lets get the best ideas and make it official when its mature. -- Julio Vinicius Protzek --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Just wanted to say: Great initiative! We need this kind of documentation that the manual and API does not (and probably should not) provide. I see three main kinds of documentation. The API = technical info on specific classes, methods, variables and things. The Manual = Descriptive info about the framework and its parts. Tutorials = Guided information in example form. I think your guide could well become the main big tutorial to get people started. Much like the first section of the so called Rails book where they go through building a basic application. /Martin On Feb 3, 7:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Zoe, Looks promising! This is an excellent idea. I've been trying to document some of this stuff over at my blog as well. I have 2 tutorials posted for 1.2 there that you're more than welcome to use to kick-start your work if you would like. http://www.keithmedlin.com/ Regards, Keith On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 4, 2008, at 10:48 AM, [EMAIL PROTECTED] wrote: I think it's a good start Zoe. I disagree with Nate on one point, I think the more examples and tutorials on Cake the better, regardless of where they exist. CakePHP desperately needs better documentation and once it has it, it's adoption rate might really skyrocket. Unfortunately this hasn't been the primary focus of the CakePHP core group and has contributed to a loss of momentum for what promises to be a great framework soluton. I side with Nate. More isn't necessarily better, and while we'll always appreciate good press, blog articles, etc what we need most is focused effort on the official docs. It's like building a skyscraper by having everyone start a small building in their own town. Any documentation is great as it provides additional perspectives on how to accomplish something. Sometimes a perspective only a few degrees shifted from the official view is enough to make things click. Again, it's a battle of good vs. best. If you think what Cake needs is docs help, your efforts are best spent in the official docs effort. In regards to the official documentation for v1.2, I think it has come along nicely. However it needs to be easier to find on the Cake site. There are no references to it on Cake's home page (that I can find) and if you click on the manual link you get the 1.1 manual. I think increasing exposure to the 1.2 manual by at least adding a link at the beginning of the online 1.1 manual (something like click here to view the in-progress manual for Cake 1.2) would expose the new manual to more users which might have the side-effect of increase outside contributions to it. We'll do that once it's done. It's still very important to realize that Cake 1.2 is beta software. I view it as a success to have so much before the final release, but I don't yet want to promote something that isn't complete yet. -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Just a suggestion, it would be nice if someone wrote in that manual ways to configure different databases. I'm having a lot of trouble using SQL Server 2005 and it's been hard to find any documentation. cheers. On 4 Feb, 13:46, Keith [EMAIL PROTECTED] wrote: Zoe, Looks promising! This is an excellent idea. I've been trying to document some of this stuff over at my blog as well. I have 2 tutorials posted for 1.2 there that you're more than welcome to use to kick-start your work if you would like. http://www.keithmedlin.com/ Regards, Keith On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 4, 2008 11:13 AM, hellfish [EMAIL PROTECTED] wrote: Just a suggestion, it would be nice if someone wrote in that manual ways to configure different databases. I'm having a lot of trouble using SQL Server 2005 and it's been hard to find any documentation. cheers. When you say configure different databases what exactly do you mean? -- Chris Hartjes Internet Loudmouth Motto for 2008: Moving from herding elephants to handling snakes... @TheKeyBoard: http://www.littlehart.net/atthekeyboard --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
The only comment or criticism I have is that it's a shame that such efforts aren't put towards the official documentation. John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I don't mean to denigrate your efforts here, but I really think that efforts like these often serve to scatter and spread the pool of useful information thinner, which just makes it harder to find, which makes people more frustrated. On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
I think it's a good start Zoe. I disagree with Nate on one point, I think the more examples and tutorials on Cake the better, regardless of where they exist. CakePHP desperately needs better documentation and once it has it, it's adoption rate might really skyrocket. Unfortunately this hasn't been the primary focus of the CakePHP core group and has contributed to a loss of momentum for what promises to be a great framework soluton. Any documentation is great as it provides additional perspectives on how to accomplish something. Sometimes a perspective only a few degrees shifted from the official view is enough to make things click. In regards to the official documentation for v1.2, I think it has come along nicely. However it needs to be easier to find on the Cake site. There are no references to it on Cake's home page (that I can find) and if you click on the manual link you get the 1.1 manual. I think increasing exposure to the 1.2 manual by at least adding a link at the beginning of the online 1.1 manual (something like click here to view the in-progress manual for Cake 1.2) would expose the new manual to more users which might have the side-effect of increase outside contributions to it. that's my 2 cents. brian fidler Quoting nate [EMAIL PROTECTED]: The only comment or criticism I have is that it's a shame that such efforts aren't put towards the official documentation. John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I don't mean to denigrate your efforts here, but I really think that efforts like these often serve to scatter and spread the pool of useful information thinner, which just makes it harder to find, which makes people more frustrated. On Feb 3, 1:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
On Feb 4, 2008, at 6:23 PM, Keith wrote: On Feb 4, 11:48 am, nate [EMAIL PROTECTED] wrote: John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I agree with Nate here. I put things on my site and document them as I find incomplete tutorials, inaccuracies, or things I flat out couldn't find suitable answers for on the internet. The file upload in 1.2 is a great case in point. The documentation that exists covers solutions to niche problems (ajax uploading, image manipulation after upload, etc.). I think if there was a roadmap for the documentation that people could sign up for and create documentation that subject it'd go much more smoothly. However, I don't see any great organizational framework to join up with other than a general call to help contribute. I think more people would step forward if they knew what topics were desired. http://cakeforge.org/plugins/wiki/index.php?id=53type=g -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
This is great. Thanks! On Feb 4, 8:41 pm, John David Anderson (_psychic_) [EMAIL PROTECTED] wrote: On Feb 4, 2008, at 6:23 PM, Keith wrote: On Feb 4, 11:48 am, nate [EMAIL PROTECTED] wrote: John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I agree with Nate here. I put things on my site and document them as I find incomplete tutorials, inaccuracies, or things I flat out couldn't find suitable answers for on the internet. The file upload in 1.2 is a great case in point. The documentation that exists covers solutions to niche problems (ajax uploading, image manipulation after upload, etc.). I think if there was a roadmap for the documentation that people could sign up for and create documentation that subject it'd go much more smoothly. However, I don't see any great organizational framework to join up with other than a general call to help contribute. I think more people would step forward if they knew what topics were desired. http://cakeforge.org/plugins/wiki/index.php?id=53type=g -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Great work John!! Really forward to reading this. On Feb 4, 8:41 pm, John David Anderson (_psychic_) [EMAIL PROTECTED] wrote: On Feb 4, 2008, at 6:23 PM, Keith wrote: On Feb 4, 11:48 am, nate [EMAIL PROTECTED] wrote: John gets little to no help from outside contributors, and the only way the community has seen fit to contribute is with scattered, one-off tutorials at various levels of currency, completeness and accuracy. I agree with Nate here. I put things on my site and document them as I find incomplete tutorials, inaccuracies, or things I flat out couldn't find suitable answers for on the internet. The file upload in 1.2 is a great case in point. The documentation that exists covers solutions to niche problems (ajax uploading, image manipulation after upload, etc.). I think if there was a roadmap for the documentation that people could sign up for and create documentation that subject it'd go much more smoothly. However, I don't see any great organizational framework to join up with other than a general call to help contribute. I think more people would step forward if they knew what topics were desired. http://cakeforge.org/plugins/wiki/index.php?id=53type=g -- John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hi Zoe, I think there is a definite need for this type clear introduction for CakePHP. Documentation is key to the success of any open-source project to help lower the barrier of entry. Please keep up the good work, as even if there is some duplication of effort in the community, we can never have too many good documents. Thanks again and good luck with this initiative. Ian. On Feb 3, 12:01 pm, MonkeyGirl [EMAIL PROTECTED] wrote: Hi! Just to let you all know, I've finally written enough of the CakePHP guide that I'm working on to warrant putting it online at last. It's available here: http://cakephp.bytenoise.co.uk/ It's only the first three chapters so far, but hopefully I should have a lot more there over the next few weeks. Any comments and constructive criticism are both welcomed. Thanks, Zoe. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: CakePHP guide
Hi Zoe, It would be cool if there is a way to subscribe to this guide, so you automatically get notified if there is an update. Anyway, good luck with this project! -- Daniel Hofstetter http://cakebaker.42dh.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com 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 -~--~~~~--~~--~--~---
