> Also, in a well-build app you should be able to separate things out > with minimal effort, once you decide that you stuffed too much into > one module.
+1 I couldn't have said it better :) On Wed, Mar 11, 2009 at 3:28 AM, Richtermeister <nex...@gmail.com> wrote: > > Also, in a well-build app you should be able to separate things out > with minimal effort, once you decide that you stuffed too much into > one module. Either way, when I read "most people separate their > projects into 2 apps" I usually assume that there's a good reason for > it and try to imitate first, rather than explore if I can be > different.. Then again, there are cases where one app is justified. > > Daniel > > > On Mar 10, 2:59 am, Fabrice B <fabrice.bernh...@gmail.com> wrote: >> When trying to architecture an application, the best is to find an >> objective justification to your design. The simplest I would suggest >> is : one crud = one module >> >> In your case, the question is : do you have a separate page to edit >> user's preferences ? Then it's a separate crud and deserves its own >> module user_preferences. Is the form of the user's preferences >> included in the "edit user" page ? Then it surely deserves to stay in >> the user module. >> >> Regards, >> >> Fabrice Bernhard >> --http://www.theodo.fr > > > -- Blue Horn Ltd - System Development http://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
