0

  1. how to implement (or use if it is supported) kind of late binding in TWIG.

  2. how to transfer variable between few renders through the same instance

here is close situation with the detailed description:

Lets imagine i have global layout template, and i have kind of widgets which are called some where in the middle of the template (probably many times - lets say avatar drawing widget in the listing of users).

lets say These widgets for their functionality need to implement some javascript code in the layout:

<header>   
 <script type="text/javascript" src="widget_avatar.js">  
</header>

so, in the twig template language i want to implement smth like:

layout.twig

<header>
    {% for script_name in scripts %}
        <script type="text/javascript" src="{{ script_name }}"></script>
    {% endfor %}
</header>
<body>
    {{ Widget('Draw_Avatar') }}

    variable below set in the widget coz both widget and layout 
    uses the same TWIG instance:

    {{ after_execution }}

</body>


draw_avatar.twig

Im widget template returning some rendered html
for my functionality i need some javascript inserted
into the "layout.twig" header
adding required javascript to the array of javascripts
{% set scripts = scripts | merge({'widget_avatar':'widget_avatar.js'}) %}

{% set after_execution = 'HELLO' %}

so, many widgets could be called, some of them may add required javascript into the array of JavaScript which should be inserted in the layout header.

twig inheritance doesn't work here coz widgets supposed to be independent and easy reusable in different templates.

BUT all templates and widgets and layouts uses the same twig instance.

I need array scripts to be used in the layout header kind of late binding.

  1. so some block of code need to be rendered in the very end of template rendering process, how i can "say" TWIG about this ?

  2. how i can transfer variable into the layout template from the widget after my widget is rendered ?

aizaz
  • 3,056
  • 9
  • 25
  • 57
Eugene
  • 1,680
  • 3
  • 14
  • 23
  • Generally speaking, it's common practice to do all processing BEFORE starting your output. Also, have you read the documentation about "extends" and "block" ? http://twig.sensiolabs.org/doc/tags/extends.html – Webberig Aug 23 '13 at 11:26
  • in case of widgets implementation "processing BEFORE" doesnt work because widgets supposed to be kind of "independent" modules whcih i can call in any template one or many times. Unfortunately with native twig this impossible to implement (neither store variable after the render nor use it later as "late binding") so i had to make a twig wrapper around ZendFramework Zend_Layout::getMvcInstance()->getView()->headScript() and will have to use zend layout + twig for the rest templates :( – Eugene Aug 27 '13 at 11:50
  • But what if one of those "independent" modules causes an exception ? Or you want to use a different layout depending on those modules' outcome ? You won't be able to handle that... However, Symfony forsees this kind of behavior, you might want to look at "embedding controllers" in the documentation: http://symfony.com/doc/current/book/templating.html – Webberig Aug 28 '13 at 12:31

0 Answers0