Re: Front-end for end-users and admins design

2010-05-20 Thread Andrei Mita
Thank you for enlightening me. I'll do some more reading and come back with questions, most probably :) On Wed, May 19, 2010 at 8:51 PM, calvin wrote: > Due to the reasons explained by WebbedIT, the best thing to do is just > use admin routing. At the minimum, the models used by your admin and

Re: Front-end for end-users and admins design

2010-05-19 Thread calvin
Due to the reasons explained by WebbedIT, the best thing to do is just use admin routing. At the minimum, the models used by your admin and end-user "apps" are going to be nearly identical, if not the behaviors/ views/elements/helper/controllers/components as well. So it just doesn't make sense bui

Re: Front-end for end-users and admins design

2010-05-19 Thread WebbedIT
I am currently developing a large app which needed an area for the site owner to administrate the site, another area for organisations to administer their content and an area for standard site users to register and maintain their profiles. At first I thought it was sensible to do 3 apps on seperat

Re: Front-end for end-users and admins design

2010-05-18 Thread Andy Dirnberger
You may want to take a look at prefix routing (admin routing prior to 1.3) http://book.cakephp.org/view/950/Prefix-Routing. On May 18, 9:58 am, Andrei Mita wrote: > Thank Renato. Actually I was thinking to develop two separate cake apps: one > to run the website for the end-users and one, nested

Re: Front-end for end-users and admins design

2010-05-18 Thread Andrei Mita
Thank Renato. Actually I was thinking to develop two separate cake apps: one to run the website for the end-users and one, nested inside the main cake app, to run the administration panel. for instance: mywebsite.com for end-users and mywebsite.com/oven for admins Any other suggestions? On Tue,

Re: Front-end for end-users and admins design

2010-05-18 Thread Renato de Freitas Freire
I like to do all the client system first, then I do another system, completly diferent to admin stuff. Even cake having the admin route, I dont like to use it. That way, I can put it in another url, so, guessing my admins urls is not a trivial thing... so, if one day, someone find a bug in cake adm

Front-end for end-users and admins design

2010-05-18 Thread Andrei Mita
Hello, I'm getting ready to start a real project using Cake and the first question is: how to separate controllers, actions and views for end-users and admins. I mean, is there a recommended way of doing the splitting or is it enough to create separate actions for end-users and for admins? For i