You can create subfolders in resources/view and multiple controllers, eventually in fe/be subnamespaces.
Yohan. Le 16 févr. 2011 18:51, "Richtermeister" <nex...@gmail.com> a écrit : > It's really the same as in symfony1 where a blog plugin would contain > a "front module" and one or more "admin modules", as well as the > entire blog model and blog specific assets. > The only thing I'm unsure about is how to group said files within the > bundle.. I mean, most bundles I see have one controllers dir and one > templates dir, etc.. but do you just mix admin vs. front-end templates > in there? > > Thanks for clarifying, > Daniel > > > On Feb 16, 9:18 am, Yohan GIARELLI <yo...@giarelli.org> wrote: >> Yes, it's right. >> >> it's more semantic and easy to use. (one routing per bundle with fe/be >> routes, etc.) >> >> Yohan. >> >> 2011/2/16 Daniel Londero <daniel.lond...@gmail.com> >> >> > On 16 Feb, 14:42, GIARELLI Yohan <yo...@giarelli.org> wrote: >> > > A *Bundle* is a structured set of files (PHP files, stylesheets, >> > > JavaScripts, images, ...) that *implements* a single feature (a blog, a >> > > forum, ...) and which can be easily shared with other developers. >> >> > > Think about creating separated controllers in your bundle to separate >> > your >> > > frontend and backend. >> >> > Thanks for the reply Yohan. I've read something similar about creating >> > separated controllers in the docs about Sf2 for sf1.x developer. >> >> > In that situation I think we need to decouple components of the app >> > (say a news section, products catalog, press releases) without >> > grouping them in fe and be but having NewsBundle, ProductsBundle, >> > PressBundle. Each of them with a second controller for be operations. >> > It looks nice because Entities are in the right place: where them will >> > be used (I'll not use News Entity in Products context). >> >> > Is it right? >> >> > 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 -- 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
