I suppose I'm talking about this:
http://book.cakephp.org/view/21/a-typical-cakephp-request
Just right now I feel it's neither high-level enough nor detailled
enough to really help. Adding code examples would be great. Following
variables/data throughout the application would help (controller/
action Cakes::buy() is being chosen because...) etc. Explaining Model
relationship declarations and where to call them from (why doesn't
ModelA->ModelB->find('all') take conditions on the association into
account).
On 25 Jun 2008, at 09:51, David C. Zentgraf wrote:
> Just the vaguest of ideas, but a section on "app flow" would be good
> I think.
>
> Which parts of Cake get called in which order, which files are
> minimally relevant to a functioning application, where all the
> automagic comes from [1] etc. I think for "traditional" PHP
> programmers [2] Cake is a huge opaque blob in the beginning. Example
> apps like the blog tutorial are helping somewhat, but you'll still
> have to piece together the big picture yourself.
>
> [1] e.g. relationship between specifying $belongsTo and the
> generated SQL
> [2] i.e. page starts at the top, includes() are easy to follow, one
> instruction after the other, page ends
>
> Chrs,
> Dav
>
> On 25 Jun 2008, at 01:11, John David Anderson wrote:
>
>>
>> Bakers,
>>
>> How are we doing? What is the most confusing? What's most needed and
>> missing? I have a punchlist of my own, but I'm looking for input from
>> you guys, especially the new ones.
>>
>> Thanks,
>>
>> John
>>
>> >>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
