The Yii framework allows developers to use their favorite template syntax (such as Prado, Smarty) to write the view of a controller or widget. This can be done through Write and install a viewRenderer application component to achieve this. This view renderer intercepts the call to CBaseController::renderFile, compiles the view file through custom template syntax, and then renders the final compiled result.
Info: It is recommended to use custom template syntax only when writing views that are rarely reused. Otherwise, reusing views in the application will force the use of the same template syntax.
Next, we will introduce how to use CPradoViewRenderer, a view renderer similar to the Prado framework that allows developers to use custom template syntax. If you want to develop your own view renderer, CPradoViewRenderer is a good guide.
CPradoViewRenderer
To use CPradoViewRenderer, we just need to configure the application as follows:
return array( 'components'=>array( ......, 'viewRenderer'=>array( 'class'=>'CPradoViewRenderer', ), ), );
By default, CPradoViewRenderer will compile source view files and save the resulting PHP files under the runtime directory. Only when the source view files are changed, will the PHP files be re-generated. Therefore , using CPradoViewRenderer incurs very little performance degradation.
Tip: While CPradoViewRenderer mainly introduces some new template tags to make writing views easier and faster, you can still write PHP code as usual in the source views.
In the following, we introduce the template tags that are supported by CPradoViewRenderer.
Short PHP tags are shortcuts to writing PHP expressions and statements in a view. The expression tag <%= expression %>
is translated into <?php echo expression ?>
; while the statement tag <% statement %>
to <?php statement ?>
. For example,
<%= CHtml::textField($name,'value'); %> <% foreach($models as $model): %>
is translated into
<?php echo CHtml::textField($name,'value'); ?> <?php foreach($models as $model): ?>
Component tags are used to insert a widget in a view. It uses the following syntax:
##
<com:WidgetClass property1=value1 property2=value2 ...> // body content for the widget </com:WidgetClass> // a widget without body content <com:WidgetClass property1=value1 property2=value2 .../>
WidgetClass specifies the widget class name or class path alias, and property initial values can be either quoted strings or PHP expressions enclosed within a pair of curly brackets. For example,
<com:CCaptcha captchaAction="captcha" showRefreshButton={false} />
<?php $this->widget('CCaptcha', array( 'captchaAction'=>'captcha', 'showRefreshButton'=>false)); ?>
Cache tagsCache tags are shortcuts to using fragment caching. Its syntax is as follows,Note: The value for showRefreshButton
is specified as
{false}instead of
"false"because the latter means a string instead of a boolean.
<cache:fragmentID property1=value1 property2=value2 ...> // content being cached </cache:fragmentID >
fragmentID should be an identifier that uniquely identifies the content being cached, and the property-value pairs are used to configure the fragment cache. For example,
<cache:profile duration={3600}> // user profile information here </cache:profile >
<?php if($this->beginCache('profile', array('duration'=>3600))): ?> // user profile information here <?php $this->endCache(); endif; ?>
<clip:clipID> // content for this clip </clip:clipID >
clipID is an identifier that uniquely identifies the clip content. The clip tags will be translated as
<?php $this->beginClip('clipID'); ?> // content for this clip <?php $this->endClip(); ?>
<!--- view comments that will be stripped off --->
.tpl, then any view file ending with
.tpl will be rendered using the installed view renderer, while all other view files ending with
.php will be treated as normal PHP view script.
The above is Yii Framework Official Guide Series 49—— Special topic: Content using non-mainstream template syntax. For more related content, please pay attention to the PHP Chinese website (www.php.cn)!