Then maybe better to split {% assetic ..., output="js AND css" %} into 2
different functions:
{% javascripts ... %}
AND
{% stylesheets ... %}
?
--------------------------------------------------Konstantin Kudryashov
(everzet)
http://about.me/everzet/bio
On пятница, 11 февраля 2011 г. at 0:00, Christophe COEVOET wrote:
Le 10/02/2011 22:32, stloyd a écrit :
> > AFAIK {% assets %} Fabien was talking about that the Assetic will be
> > an "evolution" of existing BC-asset code.
> It will not replace the current asset() function which is also used when
> including an image in your page. Assetic is only a replacement for {%
> javascripts %} and {% stylesheets %}. So the issue of similar names remains.
>
> I find rather confusing for newcomers to have an assets tag and an asset
> function. {% assets ... %} and {{ asset(...) }} look not very different
> so this might lead to some WTF when using one instead of the other.
>
> --
> 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
>
--
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
