You are lucky to hava designers to do that stuff for you... I don't at the moment. You are right, though, I do come a bit more from a usability and gui background than pure code-crunching. I guess the approach varies a lot with preference, previous experience and the surrounding team (if any)... but also a lot on the type of application one is developing.
My current work is an application with minimal gui so far. 90% of the requests never end up as a normal view. It is mostly an exposed API where service-calls go in and com out the other end. I am not very happy with the gui but since it is not really the no1 priority I can't justify a ton of work on cool javascript effects and ajax calls. I hope we will get to a GUI "module" soon. :) On Oct 24, 2:49 pm, Bernardo Vieira <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > I really dislike my work when I have "cheated" and built views after > > the models... The gui never turns out nice... feels like > > scaffolding :) > > Hehehe, interesting... The thing is this kind of approach would never > work for me. I'm a terrible designer, cake's scaffolding is waaaaaaaay > better than what I would come up with. That's why I focus on modeling > and programming and leave the views to the end, then I hand it over to > the design guys and let them make it pretty ;). Naturally this is not a > one way street. As you said tinkering the views often shapes up the > controllers, requires some javascript of ajax integration, etc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
