Re: Recommendations for changes to Cake manual.
hey I think the point is actually valid enough to warrant a ticket: https://trac.cakephp.org/ticket/4820 thanks mate - real search is high on my to-do list so don't worry :) let's say - a week ? as for the whole topic- i'm okay with it as long as proper tickets will be created :) if not - don't think that stuff will be implemented even with feedback. greets, -- Marcin Domanski http://kabturek.info --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
as for the whole topic- i'm okay with it as long as proper tickets will be created :) if not - don't think that stuff will be implemented even with feedback. Many of the features seem to be getting addressed. I was using the manual last night and the speed was much improved. I agree that some of the content should be rearranged but I think it's more important at this stage just to get everything documented. There's so much new stuff going into 1.2 that it's hard to keep up. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
Many of the features seem to be getting addressed. I was using the manual last night and the speed was much improved. yes there are ;) gwoo deployed the svn version on sunday that had many improvements. I agree that some of the content should be rearranged but I think it's more important at this stage just to get everything documented. There's so much new stuff going into 1.2 that it's hard to keep up. true -- Marcin Domanski http://kabturek.info --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
On Mon, Jun 2, 2008 at 1:20 PM, mustan9 [EMAIL PROTECTED] wrote: Hi, I have a few improvement requests for the Cake online manual. File a ticket over at trac.cakephp.org rather than place your requests in the mailing list. I can almost guarantee nothing will happen without a ticket. -- 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 CakePHP 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: Recommendations for changes to Cake manual.
I've filed tickets there before and gotten replies telling me to post things like this on the mailing list. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
On Mon, Jun 2, 2008 at 2:07 PM, mustan9 [EMAIL PROTECTED] wrote: I've filed tickets there before and gotten replies telling me to post things like this on the mailing list. I doubt that, and would be happy to take it back if you show some proof. All work on the project flows through either the ticket system or at the initiative of the core developers (disclaimer: I am a core developer who has been slacking off in the initiative department as of late). If people want to rant and rave in the mailing list, all the power to you. But don't lie about the reasons for not filing tickets please. If someone did indeed tell that to you before, don't let one bad apple spoil the whole bunch. -- 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 CakePHP 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: Recommendations for changes to Cake manual.
I agree with Chris' suggestion on creating tickets, but let me quickly respond here as well to see what others think... On Jun 2, 2008, at 11:20 AM, mustan9 wrote: Hi, I have a few improvement requests for the Cake online manual. 1) Currently, CakePHP.org is using Google to perform searching of the online manual. This doesn't work very well, and if you enter the value model it returns lots of unrelated links outside the scope of the manual. I would prefer that searching for model in the manual would return a list of pages with that word sorted by priority. The Google search was low hanging fruit for us, so we used it. We want to make the search better, but this was an easy way to get a lot of functionality fast. I think we won't entertain enhancing it unless someone can help us out with creating the changes. I also think if you're just searching for model, you're not going to get great search results anyway. This can be mitigated by smarter querying (ala model associations, model behaviors, or supermodels). 2) The manual mixes tutorial sections and reference sections. It's a little confusing. If you want to look up how to perform validation in a model it's hidden under 4 Common Tasks With CakePHP / Data Validation. You've separated models and validation into two different sections of the manual. Since the model documentation is located under Developing with CakePHP / Models. I guess I need a community response here - we've organized it as best we can, but this is the first time this has been brought up. If I get the feeling the current outline isn't' worried, we'll change it. Thoughts, folks? 3) Developing with CakePHP is really documentation for the API. It's structured differently from other sections of the manual. For example; All the subsections are really API objects. This really should be made a separate manual. There should be a tutorial manual, and a reference manual. If I need to know how to do a findAll with a model I look in the reference manual, and if I need to know how to install Cake on a shared server then I look in the tutorial manual under Installing Cake. The line between helping people use the API, and see the big picture tasks is really fuzzy. We don't really have any good answers here, but let me at least say that first, I don't see the advantage in splitting it up. Also, tutorials are housed in the Bakery, the manual houses a few fundamentals that are almost universally requested for (a starter tute, and an auth tute). 4) Allow short cuts to access reference material quickly; Nothing worse then having to browse all the subcategories of the manual to find where you've put the documentation for models. Do you have some specific suggestions for making this work? 5) Add see also links for the reference manual. If I'm reading the findBy documentation I'd like to also see a see also; findAll link for anything related. Yeah, good idea (make sure that gets logged). 6) Allow anonymous editing of the manual. Do you really need some one to register in order to submit a fix for a spelling mistake in the documentation? Yes. That is, unless you want to read about body enhancements, online pharmacies, and/or adult websites inside the manual. There *is* an approval process, but we want the threshold a little higher than rock bottom. 7) Change the Table Of Contents to use AJAX so that our browsers don't refresh every time we browse the tree. You'd need to clarify your suggestion here - I'm not sure what you mean. 8) Package the manual as a down loadable off line resource that people can read on the go. Such as a with a laptop while on the train headed to work. This has been covered on the list before - search it up for some ideas on how to accomplish this. I'm also toying with the idea of offering a nice printed version of the manual as a desk reference, possibly with some extra chapters from core team guys or other wildly popular celebrities. Thanks for the input, John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
If people want to rant and rave in the mailing list, all the power to you. But don't lie about the reasons for not filing tickets please. If you wish to have an argument about the truthfulness of my posts, then I recommend we move this to a private exchange of e-mails. My e- mail address is publicly shown with all my posts. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
On Mon, Jun 2, 2008 at 3:41 PM, mustan9 [EMAIL PROTECTED] wrote: If you wish to have an argument about the truthfulness of my posts, then I recommend we move this to a private exchange of e-mails. My e- mail address is publicly shown with all my posts. So is mine. What's your point exactly? I have no desire to continue this exchange in private emails because it does not serve my purposes. The purpose of my email is to tell people FILE TICKETS IF YOU WANT TO SEE THINGS CHANGE. I repeat my request to be shown proof that when filing tickets to do with the manual you have been told to not file a ticket but to discuss it on the mailing list instead. I also repeat my statement that if this was the case I will be glad to say I was wrong and credit you for being correct. People can say what they want about me, but I do tend to stick with what I say in my e-mails. If I am wrong, I'll do a blog post apology where many people can see it. Seriously, when did his happen because that is not current ticket-responding policy as far as I am aware. -- 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 CakePHP 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: Recommendations for changes to Cake manual.
mustan9 ha escrito: Hi, I have a few improvement requests for the Cake online manual. snip 7) Change the Table Of Contents to use AJAX so that our browsers don't refresh every time we browse the tree. since that is js only - please attach a patch with your ticket. cheers, AD --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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: Recommendations for changes to Cake manual.
On 3 Jun 2008, at 04:03, John David Anderson wrote: The Google search was low hanging fruit for us, so we used it. We want to make the search better, but this was an easy way to get a lot of functionality fast. I think we won't entertain enhancing it unless someone can help us out with creating the changes. I think the point is actually valid enough to warrant a ticket: https://trac.cakephp.org/ticket/4820 or supermodels There is supermodel support planned for Cake? Sweet! Chrs, Dav --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups CakePHP 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 -~--~~~~--~~--~--~---
