KEMBAR78
7.1 Initialise The View Scripts: Namespace Use Use Class Extends Public Function | PDF | Areas Of Computer Science | Computer Programming
Scribd
Upload
43 views2 pages

7.1 Initialise The View Scripts: Namespace Use Use Class Extends Public Function

The document discusses setting up a controller in Zend Framework 2. It explains that a controller class must implement the Zend\Stdlib\Dispatchable interface and can extend the AbstractActionController abstract class. The controller class is named {ControllerName}Controller and stored in {ControllerName}Controller.php. Each action method starts with a lowercase name followed by Action, like indexAction(). Four actions - index, add, edit, and delete - are defined for an AlbumController class.

Uploaded by

Holly Anderson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
43 views2 pages

7.1 Initialise The View Scripts: Namespace Use Use Class Extends Public Function

The document discusses setting up a controller in Zend Framework 2. It explains that a controller class must implement the Zend\Stdlib\Dispatchable interface and can extend the AbstractActionController abstract class. The controller class is named {ControllerName}Controller and stored in {ControllerName}Controller.php. Each action method starts with a lowercase name followed by Action, like indexAction(). Four actions - index, add, edit, and delete - are defined for an AlbumController class.

Uploaded by

Holly Anderson
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

We are now ready to set up our controller.

In Zend Framework 2, the controller is a class


that is generally called
{Controller name}Controller. Note that {Controller name} must start with a capital letter.
This
class lives in a file called {Controller name}Controller.php within the Controller directory
for the
module. In our case that is module/Album/src/Album/Controller. Each action is a public
method within
the controller class that is named {action name}Action. In this case {action name}
should start with a
lower case letter.
Note: This is by convention. Zend Framework 2 doesnt provide many restrictions on
controllers other
than that they must implement the Zend\Stdlib\Dispatchable interface. The framework
provides
two abstract classes that do this for us: Zend\Mvc\Controller\AbstractActionController
and Zend\Mvc\Controller\AbstractRestfulController. Well be using the standard
AbstractActionController, but if youre intending to write a RESTful web service,
AbstractRestfulController may be useful.
Lets go ahead and create our controller class AlbumController.php at
zf2-tutorials/module/Album/src/Album/Controller :
1 namespace Album\Controller;
2
3 use Zend\Mvc\Controller\AbstractActionController;
4 use Zend\View\Model\ViewModel;
5
6 class AlbumController extends AbstractActionController
7 {
8 public function indexAction()

9{

10 }
11
12 public function addAction()
13 {
14 }
15
16 public function editAction()
17 {
18 }
19
20 public function deleteAction()
21 {
22 }

23 }

17
Zend Framework 2 Documentation, Release 2.2.5dev
Note: We have already informed the module about our controller in the controller
section of
module/Album/config/module.config.php.
We have now set up the four actions that we want to use. They wont work yet until we
set up the views. The URLs
for each action are:
URL Method called
http://zf2-tutorial.localhost/album Album\Controller\AlbumController::indexAction
http://zf2-tutorial.localhost/album/add Album\Controller\AlbumController::addAction
http://zf2-tutorial.localhost/album/edit Album\Controller\AlbumController::editAction
http://zf2-tutorial.localhost/album/delete Album\Controller\AlbumController::deleteAction
We now have a working router and the actions are set up for each page of our
application.
Its time to build the view and the model layer.
7.1 Initialise the view scripts
To integrate the view into our application all we need to do is create some view script
files. These files will be
executed by the DefaultViewStrategy and will be passed any variables or view models
that are returned from
the controller action method. These view scripts are stored in our modules views
directory within a directory named
after the controller. Create these four empty files now:
module/Album/view/album/album/index.phtml
module/Album/view/album/album/add.phtml
module/Album/view/album/album/edit.phtml
module/Album/view/album/album/delete.phtml
We can now start filling everything in, starting with our database and models.

You might also like