On Sun, Mar 9, 2008 at 12:20 AM, DragonI <[EMAIL PROTECTED]> wrote: > > I agree with Woodsman. But it's a nice to have. I think the goal > should be to complete the "manual" 1st. > > Chris using your logic, what's the use of the 2 books coming out if > 1.2 isn't finalized yet? >
Is that not a valid point though? The poor schmuck writing that book will get flamed up and down the list when the book comes out and something in Cake has changed since it was published. "I tried the example of page 134 of the new Cake Book and I get the following error message, why won't it work. blah blah blah". Good luck with that. There is supposed to be a "give" to go with the "take" when you use an open source project. I have "taken" lots from Cake and have tried to "give" back via my blog and some small code contributions that have made their way into the core (mainly console-related stuff). I don't feel like I'm off-base when I suggest to people that if they want to see something (say, a PDF version of the API) then feel free to DO IT YOURSELF and if you feel like sharing, well, that's even better. Giving back to an open source project is something that helps push it forward, regardless of how small the contribution is. Nate and John have expressed my views quite succinctly in other messages in this thread. Don't start allocating other people's time for them, and show some patience and respect for the huge amount of work that has gone into creating the cookbook *and* API. Before people get all up in arms and claim they are not dissing John's efforts, think again. Chiming in with a "me too" email when someone says (warning, sarcasm and paraphrasing ahead) "why won't someone other than me create a PDF of some documentation for Cake" is not the way to get these things done. Like my old man always said to me "it's about results, you lazy kid!" Any volunteers to be the PDF wrangler? Don't be shy, step forward... So, if someone wants to generate their own copy of the Cookbook or API in PDF form and make it available as a download to anyone who wants and updates it every time the Cookbook or API changes, well, that's their choice. It will also be a very welcome contribution by other people. But insisting that others have to do it is wrong. 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 [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 -~----------~----~----~----~------~----~------~--~---
