Aug
10
Zend Framework – View Layer ”; Previous Next A View Layer is the presentation layer of the MVC application. It separates the application logic from the presentation logic. In a typical PHP web application, all business logic and design are intermixed. Intermixing enables faster development in a small project. But, it fails miserably in large project, where lot of high level architecture is involved. To change the design of the web application, a developer needs to work on the business logic as well. This may be catastrophic resulting in breaking of business logic. Zend Framework provides a well thought, clean, flexible and extendable View layer. The View layer is available as a separate module, Zend/View and integrate fine with Zend/Mvc module. The Zend View Layer is separated into multiple components interacting nicely with each other. Its various components are as follows − Variables Containers − Holds view layer”s data. View Models − Holds Variable Containers and design template. Renderers − Process data and template from View Model and output a design representation, maybe the final html output. Resolvers − Resolves template available in the View Model in such a way that the Renderer can consume. View (ZendViewView) − Maps request to the renderer and then renderer to response. Rendering Strategies − Used by View to map request to renderer. Response Strategies − Used by View to map renderer to response. The view layer, View processes the ViewModel, resolves the template using a Resolver, render it using Rendering Strategy and finally outputs it using the Response Renderer. View Layer Configuration Like the controller, a View layer can be configured in a module”s configuration file called as – module.config.php. The main configuration is to specify where the templates are going to be placed. This can be accomplished by adding the following configuration in the “module.config.php”. ”view_manager” => [ ”template_path_stack” => [”tutorial” => __DIR__ . ”/../view”,], ] By default, the View layer has a default behavior for all its components. For example, a ViewModel resolves the template name of a controller”s action inside the template root by “lowercase-module-name/lowercase-controller-name/lowercase-action-name” rule. However, this can be overridden by the setTemplate() method of the ViewModel. Controllers and View Layer By default, a controller does not need to send any data to the view layer. It is enough to write the template in the proper place. For example, in our example, TutorialController, the template needs to be placed at myapp/module/Tutorial/view/tutorial/tutorial/index.phtml. The index.phtml refers the PHP based template and it will be rendered by the PHPRenderer. There are other renderer’s such as JsonRenderer for json output and FeedRenderer for rss and atom output. The complete listing is as follows − <?php namespace TutorialController; use ZendMvcControllerAbstractActionController; use ZendViewModelViewModel; class TutorialController extends AbstractActionController { public function indexAction() { } } Zend Application Template <div class = “row content”> <h3>This is my first Zend application</h3> </div> Finally, we have successfully completed the Tutorial module and we can access it using url – http://localhost:8080/tutorial. Passing Data to View Layer The simplest way to send the data to a view layer is to use the ViewModel arguments. The changed indexAction method is as follows − public function indexAction() { $view = new ViewModel([ ”message” => ”Hello, Tutorial” ]); return $view; } Now, change the index.phtml file as follows − <div class = “row content”> <h3>This is my first Zend application</h3> <h4><?php echo $this->message?></h4> </div> View Helpers A View Helper is used to write small, atomic functions to be used in templates. Zend framework provides an interface, ZendViewHelperHelperInterface to write standard view helpers. A HelperInterface has just two methods, setView() − This method accepts a ZendViewRendererRendererInterface instance/implementation. getView() − It is used to retrieve that instance. The complete code listing of HelperInterface is as follows − namespace ZendViewHelper; use ZendViewRendererRendererInterface as Renderer; interface HelperInterface { /** * Set the View object * * @param Renderer $view * @return HelperInterface */ public function setView(Renderer $view); /** * Get the View object * * @return Renderer */ public function getView(); } To use a helper in your view script, access it using $this->helperName(). Built-in Helpers Zend Framework provides a lot of inbuilt helper function for various purposes. Some of the View Helpers available in the zend-mvc are as follows − URL URL helper is used to generate the URLs matching the routes defined in the application. The definition of the URL helper is − $this->url($name, $params, $options, $reuseMatchedParameters) For example, in the tutorial module, the route is named as tutorial and it has two parameters action and id. We can use URL helper to generate two different URLs as shown below − <a href = “<? = $this->url(”tutorial”); ?>”>Tutorial Index</a> <a href = “<? = $this->url(”tutorial”, [”action” => ”show”, ”id” =>10]); ?>”> Details of Tutorial #10 </a> The result will be as follows − <a href = “/tutorial”>Tutorial Index</a> <a href = “/tutorial/show/10″> Details of Tutorial #10</a> Placeholder Placeholder helper is used to persist content between view scripts and view instances. It provides option to set data initially and then use it in later stages. For example, we can set, say company name and then use it in all other places. <?php $this->placeholder(”companyname”)->set(“TutorialsPoint”) ?> <?= $this->placeholder(”companyname”); ?> A Placeholder provides some of the advanced options to generate complex content from PHP array and objects. It also has option to capture certain section of the template itself. For example, the following code captures the template result in between and stores it in the productlist placeholder. Class – Product class Product { public $name; public $description; } Controller $p1 = new Product(); $p1->name = ”Car”; $p1->description = ”Car”; $p2 = new Product(); $p2->name = ”Cycle”; $p2->description = ”Cycle”; $view = new ViewModel([”products” => $products]); Template <!– start capture –> <?php $this->placeholder(”productlist”)->captureStart(); foreach ($this->products as $product): ?> <div> <h2><?= $product->name ?></h2> <p><?= $product->description ?></p> </div> <?php endforeach; ?> <?php $this->placeholder(”productlist”)->captureEnd() ?> <!– end capture –> <?= $this->placeholder(”productlist”) ?> Result <div class = “foo”> <h2>Car</h2> <p>Car</p> </div> <div class = “foo”> <h2>Cycle</h2> <p>Cycle</p> </div> Doctype The Doctype