The probem for us is that we don't know which assets we need for each request, as our CMS application is a platform for multiple sites, each of which can use a random selection of widgets with their own JS/CSS. We could compile the assets with assetic for each site, but would still need a way for each widget to declare its asset dependencies.
I made this: https://github.com/ylly/YllyAssetDependencyBundle Far from perfect but it works for now. On Fri, 2011-12-23 at 04:20 -0800, Alexandre Salomé wrote: > Hello, > > > You are missing Assetic. The main advantage of Assetic is to generate > assets *before* any action. You should consider using Assetic and/or > work on it. > > > With your solution, it includes "dynamic" stylesheets, depending of > which blocks are displayed. > > > > > Best regards, > > > Alexandre -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
