Home  >  Article  >  Backend Development  >  Detailed explanation of the methods of creating views and rendering views in PHP's Yii framework

Detailed explanation of the methods of creating views and rendering views in PHP's Yii framework

高洛峰
高洛峰Original
2017-02-06 17:25:431365browse

Views are part of the MVC pattern. It is the code that displays data to end users. In web applications, views are created based on view templates. The view template is a PHP script file, which mainly contains HTML code and display PHP code, and is managed through the yii\web\View application component. This component mainly provides general methods to help view construction and rendering. For simplicity, we call the view template or view template file a view.

Create View

As mentioned before, the view is a PHP script containing HTML and PHP code. The following code is a view of a login form. You can see that the PHP code is used to generate dynamic content, such as Page title and form, HTML code organizes it into a beautiful HTML page.

<?php
use yii\helpers\Html;
use yii\widgets\ActiveForm;
 
/* @var $this yii\web\View */
/* @var $form yii\widgets\ActiveForm */
/* @var $model app\models\LoginForm */
 
$this->title = &#39;Login&#39;;
?>
<h1><?= Html::encode($this->title) ?></h1>
 
<p>Please fill out the following fields to login:</p>
 
<?php $form = ActiveForm::begin(); ?>
  <?= $form->field($model, &#39;username&#39;) ?>
  <?= $form->field($model, &#39;password&#39;)->passwordInput() ?>
  <?= Html::submitButton(&#39;Login&#39;) ?>
<?php ActiveForm::end(); ?>

In the view, you can access $this to point to yii\web\View to manage and render this view file.

In addition to $this, the view in the above example has other predefined variables such as $model. These variables represent data passed to the view from the controller or other objects that trigger the rendering of the view.

Tips: List the predefined variables in the header comment of the view file so that they can be recognized by the IDE editor. It is also a good way to generate view documents.
Security

When creating views that generate HTML pages, it is important to transcode and filter user input data before displaying it, otherwise, your application may be vulnerable to cross-site scripting attacks.

To display plain text, first call yii\helpers\Html::encode() for transcoding. For example, the following code transcodes the user name before displaying it:

<?php
use yii\helpers\Html;
?>
 
<div class="username">
  <?= Html::encode($user->name) ?>
</div>

To display HTML Content, first call yii\helpers\HtmlPurifier to filter the content. For example, the following code will filter the submitted content before displaying it:

<?php
use yii\helpers\HtmlPurifier;
?>
 
<div class="post">
  <?= HtmlPurifier::process($post->text) ?>
</div>

Tips: HTMLPurifier does a good job of ensuring the security of the output data, but its performance is not good. If your application requires high performance, consider caching the filtered results.

Organization View

Similar to controllers and models, there are some conventions on organizing views:

The view files rendered by the controller are placed by default at @app/views/ControllerID directory, where ControllerID corresponds to the controller ID. For example, the controller class is PostController, the view file directory should be @app/views/post, and the directory corresponding to the controller class PostCommentController is @app/views/post-comment. If it is in a module controller, the directory should be the views/ControllerID directory under the yii\base\Module::basePath module directory;
The view files for widget rendering are placed in the WidgetPath/views directory by default, where WidgetPath represents the location of the widget class file directory;
For view files rendered by other objects, it is recommended to follow similar rules to widgets.
You can override the yii\base\ViewContextInterface::getViewPath() method of the controller or widget to customize the default directory of view files.

Render view

The render view method can be called in the controller, widget, or elsewhere to render the view. The method is similar to the following format:

/**
 * @param string $view 视图名或文件路径,由实际的渲染方法决定
 * @param array $params 传递给视图的数据
 * @return string 渲染结果
 */
methodName($view, $params = [])

Rendering in the controller

In the controller, you can call the following controller methods to render the view:

yii\base\Controller::render(): Render a view name and use a layout to return the rendering result .

yii\base\Controller::renderPartial(): Renders a view name and does not use layout.

yii\web\Controller::renderAjax(): Renders a view name without using layout, and injects all registered JS/CSS scripts and files, usually used in response to AJAX web page requests.

yii\base\Controller::renderFile(): Render a view file in a view file directory or alias.

For example:

namespace app\controllers;
 
use Yii;
use app\models\Post;
use yii\web\Controller;
use yii\web\NotFoundHttpException;
 
class PostController extends Controller
{
  public function actionView($id)
  {
    $model = Post::findOne($id);
    if ($model === null) {
      throw new NotFoundHttpException;
    }
 
    // 渲染一个名称为"view"的视图并使用布局
    return $this->render(&#39;view&#39;, [
      &#39;model&#39; => $model,
    ]);
  }
}

Widget
A widget is an instance of CWidget or its subclass. It is a component mainly used to represent data. Widgets are usually embedded in a view To generate some complex and independent user interfaces. For example, a calendar widget can be used to render a complex calendar interface. Widgets make the user interface more reusable.

We can use a view script as follows Widgets:

<?php $this->beginWidget(&#39;path.to.WidgetClass&#39;); ?>
...可能会由小物件获取的内容主体...
<?php $this->endWidget(); ?>

or

<?php $this->widget(&#39;path.to.WidgetClass&#39;); ?>

The latter is used for components that do not require any body content.

Widgets can be configured to customize their performance. This is done through This is done by calling CBaseController::beginWidget or CBaseController::widget to set its initialization property value. For example, when using the CMaskedTextField widget, we want to specify the mask to be used (can be understood as an output format, translator's note). We This is achieved by passing an array carrying the initialization values ​​​​of these properties. The key of the array here is the name of the property, and the value of the array is the value corresponding to the widget property. As shown below:

<?php
$this->widget(&#39;CMaskedTextField&#39;,array(
  &#39;mask&#39;=>&#39;99/99/9999&#39;
));
?>

Inheritance CWidget and override its init() and run() methods, you can define a new widget:

class MyWidget extends CWidget
{
  public function init()
  {
    // 此方法会被 CController::beginWidget() 调用
  }
  
  public function run()
  {
    // 此方法会被 CController::endWidget() 调用
  }
}

The widget can have its own view like a controller. By default, the widget's view The file is located under the views subdirectory of the directory that contains the widget class files. These views can be rendered by calling CWidget::render(), which is very similar to the controller. The only difference is that the widget's view does not have layout file support . In addition, $this in the widget view points to the widget instance rather than the controller instance.

Rendering in a view

You can render another view in a view by calling the following method provided by the yii\base\View view component:

yii\base\View: :render(): Render a view name.

yii\web\View::renderAjax(): 渲染一个 视图名 并注入所有注册的JS/CSS脚本和文件,通常使用在响应AJAX网页请求的情况下。

yii\base\View::renderFile(): 渲染一个视图文件目录或别名下的视图文件。

例如,视图中的如下代码会渲染该视图所在目录下的 _overview.php 视图文件, 记住视图中 $this 对应 yii\base\View 组件:

<?= $this->render(&#39;_overview&#39;) ?>

其他地方渲染

在任何地方都可以通过表达式 Yii::$app->view 访问 yii\base\View 应用组件, 调用它的如前所述的方法渲染视图,例如:

// 显示视图文件 "@app/views/site/license.php"
echo \Yii::$app->view->renderFile(&#39;@app/views/site/license.php&#39;);

更多PHP的Yii框架中创建视图和渲染视图的方法详解相关文章请关注PHP中文网!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn