Implement SmartyViewRenderer

[qiangxue]

No description provided.

[oherych]

Smarty like main or additional ViewRenderer?

[samdark]

Additional.

[oherych]

fooh, you reassured me

[sensorario]

We could use each renderer we want?

[samdark]

Yes. One at a time with fallback to plain PHP.

[cebe]

Yes. One at a time with fallback to plain PHP.

Why not choose renderer by file extension?

[rawtaz]

Just a note on choosing renderer by file extension; I've seen people needing to use a specific renderer even though the file extensions of their view files didn't match that renderer. I wouldn't think it's a good idea to lock it down to file suffix.

[samdark]

@rawtaz it's not using suffixes like in 1.1 anymore. In the controller you have to specify it explicitly:

public function actionSmarty()
{
    echo $this->render('renderer.tpl', array('username' => 'Alex'));
}

[rawtaz]

@samdark Thank you for pointing that out. I think the thing I mentioned might still apply though, if the/which renderer to use would be decided by looking at the file suffix in the first argument to render.

[samdark]

@rawtaz nope. Renderer is an application component. There's no sense in using both Smarty and Twig in a single application so user will be able to configure one renderer at a time.

[rawtaz]

@samdark All I can say is that this was not the case for the user I was thinking about. I don't remember the specifics (can probably look it up if needed).

Regardless, why would there not possibly be circumstances where one needs to render views of different types? You could have for example a system that renderPartial()s some views from other systems, e.g. the system itself uses regular PHP views but it needs to renderPartial() Smarty or Twig views provided by some other party.

EDIT: And in relation to that, there might be cases where the view file to render doesn't have a file suffix that precisely matches the renderer's default.

[cebe]

Maybe there could be a paramater like cacheId to specify the application component to be used as the renderer

[samdark]

Will check what I can do with it...

[qiangxue]

Renderer is no longer an application component, but a property of the "view" application component.

For needs like using multiple renderers simultaneously, you can create a wrapper renderer. Within this renderer you can write whatever logic in determining which render to use. We may consider providing such a wrapper renderer in the core which by default chooses view renderer by view file extension.

[samdark]

Basic implementation done. Also implemented CompositeViewRenderer that allows using multiple renderers at once with the following config:

'components' => array(
    'view' => array(
        'class' => 'yii\base\View',
        'renderer' => array(
            'class' => 'yii\renderers\CompositeViewRenderer',
            'renderers' => array(
                'tpl' => array(
                    'class' => 'yii\renderers\SmartyViewRenderer',
                ),
                'twig' => array(
                    'class' => 'yii\renderers\TwigViewRenderer',
                ),
            ),

            // that's how to use only one renderer
            //'class' => 'yii\renderers\TwigViewRenderer',
        ),
    ),
),