That's sorta how I do it. I generally start by writing a database schema in a text editor in the form of CREATE TABLE statements (I'm curious how others define and update their schemas); then I create the database and tables; then I bake the models, controllers, and views. In the past, I often stopped at this point to design the layout, but recently I've found it better to just go ahead and prototype the application using Cake's stock layout since my projects never have a fixed specification, and I may find that my original layout with room for only 6 main menu items needs to be changed to accommodate 12 menu items--that, and I tend to spend an inordinate amount of time tweaking a layout once I get started.
The coding usually begins with the controllers. I tend to think of an application in terms of what controllers/sections there are and what actions the user needs to perform in each controller. I find that this style of coding forces me to think in a top-down fashion, so I will code the controller actions using model methods that have yet to be written, then write the model methods afterward. Though, to be honest, I was mainly a fat-controller/skinny-model developer in the past, and I still have that tendency. So half the time I still end up with huge bloated controller actions that I have to go back and refactor, moving large chunks of the code to the model. Throughout most of this process, I rely on the stock cake views, which I often re-bake when new controllers are added/removed. I try to avoid any front-end development unless I need to create a custom UI element or a non-standard CRUD operation. The site is mostly REST-based until the business logic is completed. Then finally I go on to customize the UI and create the AJAX interface. On Apr 24, 12:02 pm, Renato de Freitas Freire <[email protected]> wrote: > In my case, I create the database first... > then I bake the project in cakephp.. > then, I created the layout (css, images, menus) > then I start to work with controllers and views.. > I work on controllers, and action by action, when its ready, I create the > view to test it. > once its all done, i work on auth and acl if the project needs it... > > thats the way I work on my projects... not only in cakephp, but any > language/framework... > > -- > Renato de Freitas Freire > [email protected] > > > > On Sat, Apr 24, 2010 at 6:51 AM, viis <[email protected]> wrote: > > > Would like to know what is your workflow when you start a new cakephp > > project from zero, > > > do you start from > > - making CSS and views > > - later create databases - models, > > - and leave the controllers last , > > > or you work with views, controllers, models simultaneously piece by > > piece > > > or in what order do you work > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others > > with their CakePHP related questions. > > > 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]<cake-php%[email protected]>For > > more options, visit this group at > >http://groups.google.com/group/cake-php?hl=en > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others with > their CakePHP related questions. > > 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 > athttp://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. 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
