I think that all tutorial examples assumes that you have only two applications: frontend and backend (or even single frontend). Obviously, if you have three or more applications - it will be better, if you put application classes separately. I'm not so sure about modules, but application level should rather clean.
2010/4/23 Richtermeister <nex...@gmail.com>: > Hi all, > > This is more of an aesthetic question.. > > In most tutorials/examples/apps I see written in symfony, all class > files are stored in the project/lib data. > For the model layer I see that that's a good central spot, however, I > often have forms or filters that are really only applicable to one > application, and seeing that my project/lib dirs can get pretty > crammed, I'm wondering if it's ok to move application specific classes > into the project/apps/whatever/lib realm.. or even into the lib dir > that is specific to a module.. > > Thanks for any validation either way. > > Daniel > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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 > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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