Laravel Starter - PHP User Group (Myanmar)

Laravel Starter
Let's get started by creating the folder application/views/users/. This folder will store
all of the views for our users controller. It is a standard convention to create a folder under
application/views for each controller that needs a view. Then, create the view file at
application/views/users/index.blade.php. The convention is to name the view file
after the controller action in which it's used. In this example, we're using Blade. If you do not
wish to use Blade simply name the file index.php.
Let's fill the view with the following HTML:
Users
Real Name - Email
It's not pretty. But, it's easy to understand.
Now, we'll make a modification to the users controller's index action:
public function action_index()
{
return View::make('users.index');
}
Now, where we were previously returning a string, we'll return a View object. Let's take a closer
look at what's happening here.
The View class' make() method is a factory method that is used to generate View objects. In this
case, we're passing the argument users.index. This is Laravel's internal notation for referring
to view files. The notation is made up of the path to the view file relative to the application/
views directory including the filename without its file extension. For example, application/
views/users/index.php would be written as users.index, and application/views/
admin/users/create.php would be written as admin.users.create.
It's important to note that we're returning the View object instead of using
echo to send the rendered contents of the view to the browser. This is an
important aspect of the way that Laravel works. We'll never use echo from
within a routed closure or a controller action. Instead, we'll always return
the result and allow Laravel to handle things appropriately.
Now, when we go to http://myfirst.dev/users, we'll see the view that we just created!
17