Le 06/01/2011 02:32, ryan weaver a écrit :
Hey-
So, this will work, but not exactly how you're asking. The Resources
files is just a convenient way of grouping files that come from a
variety of *very* different systems - templates, configuration, css/js
assets, translations, etc. Documentation on overriding in general
(especially overriding by placing things in your `app` dir) is
forthcoming.
So, I'm not sure if it's totally feasible. But I defer to others.
In a related note, I started to write how all of this could be done,
but quickly found myself in a pickle. Namely, I think a lot of making
one bundle override portions of another comes down to the order in
which they're initialized in AppKernel. But thinking now, I feel like
you'd need to put bundle A before bundle B (they'd need the same
actual bundle names to override templates) to override its templates,
but you'd need bundle A *after* bundle B to override its configuration
and translations. I *could* be wrong here - quick somebody try it!
Thanks
Ryan Weaver
Lead Programmer - iostudio - Nashville, TN
http://www.iostudio.com
http://www.thatsquality.com
Twitter: @weaverryan
You don't need to declare the bundle in AppKernel to override templates.
For rendering a template for Hellobundle the templating component will
look at a HelloBundle directory under app/views and then under each of
the bundle dirs (so Application first then Bundle and finally
vendor/symfony/src/Symfony/Bundle if you use the sandbox configuration)
--
Christophe | Stof
--
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 developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
