codebright

Responses 60
13
14 This is the perfect response!
15
16 ';
17 });
Awesome! Now you see the power and grace of Laravel… just kidding. We don’t want to serve
HTML this way. Embedding logic would get annoying and, more importantly, it’s just plain wrong!
Luckily for us, Laravel has a number of Response objects that make returning a meaningful reply a
whole lot easier. Let’s check out the View response since that’s the most exciting one!
Views
Views are the visual part of your application. Within the Model View Controller pattern they make
up the View portion. That’s why they are called views. It’s not rocket science. Rocket science will be
covered in a later chapter.
A view is just a plain text template that can be returned to the browser, though it’s likely that
your views will contain HTML. Views use the .php extension and are normally located within the
app/views directory. This means that PHP code can also be parsed within your views. Let’s just create
a very simple view for now.
1
2
3
4
5
6
7 Views!
8
9
10 Oh yeah! VIEWS!
11
12
Great! A tiny bit of HTML stored in app/views/simple.php. Now let’s make a view.
Didn’t we just do that?
Haha! Yes you did little one, but I didn’t mean ‘Let’s make another view file.’. Instead let’s make()
a new view response object based upon the view file we just created. The files representing views
can be called templates. This may help you distinguish between the View objects and the HTML
templates.