Commit | Line | Data |
d442cc9f |
1 | =head1 NAME |
2 | |
3ab6187c |
3 | Catalyst::Manual::Tutorial::02_CatalystBasics - Catalyst Tutorial - Chapter 2: Catalyst Application Development Basics |
d442cc9f |
4 | |
5 | |
6 | =head1 OVERVIEW |
7 | |
4b4d3884 |
8 | This is B<Chapter 2 of 10> for the Catalyst tutorial. |
d442cc9f |
9 | |
10 | L<Tutorial Overview|Catalyst::Manual::Tutorial> |
11 | |
12 | =over 4 |
13 | |
14 | =item 1 |
15 | |
3ab6187c |
16 | L<Introduction|Catalyst::Manual::Tutorial::01_Intro> |
d442cc9f |
17 | |
18 | =item 2 |
19 | |
3ab6187c |
20 | B<02_Catalyst Basics> |
d442cc9f |
21 | |
22 | =item 3 |
23 | |
3ab6187c |
24 | L<More Catalyst Basics|Catalyst::Manual::Tutorial::03_MoreCatalystBasics> |
d442cc9f |
25 | |
26 | =item 4 |
27 | |
3ab6187c |
28 | L<Basic CRUD|Catalyst::Manual::Tutorial::04_BasicCRUD> |
d442cc9f |
29 | |
30 | =item 5 |
31 | |
3ab6187c |
32 | L<Authentication|Catalyst::Manual::Tutorial::05_Authentication> |
d442cc9f |
33 | |
34 | =item 6 |
35 | |
3ab6187c |
36 | L<Authorization|Catalyst::Manual::Tutorial::06_Authorization> |
d442cc9f |
37 | |
38 | =item 7 |
39 | |
3ab6187c |
40 | L<Debugging|Catalyst::Manual::Tutorial::07_Debugging> |
d442cc9f |
41 | |
42 | =item 8 |
43 | |
3ab6187c |
44 | L<Testing|Catalyst::Manual::Tutorial::08_Testing> |
d442cc9f |
45 | |
46 | =item 9 |
47 | |
3ab6187c |
48 | L<Advanced CRUD|Catalyst::Manual::Tutorial::09_AdvancedCRUD> |
3533daff |
49 | |
50 | =item 10 |
51 | |
3ab6187c |
52 | L<Appendices|Catalyst::Manual::Tutorial::10_Appendices> |
d442cc9f |
53 | |
54 | =back |
55 | |
56 | |
57 | =head1 DESCRIPTION |
58 | |
4b4d3884 |
59 | In this chapter of the tutorial, we will create a very basic Catalyst |
60 | web application, demonstrating a number of powerful capabilities, such |
61 | as: |
d442cc9f |
62 | |
63 | =over 4 |
64 | |
65 | =item * Helper Scripts |
66 | |
67 | Catalyst helper scripts that can be used to rapidly bootstrap the |
68 | skeletal structure of an application. |
69 | |
70 | =item * MVC |
71 | |
72 | Model/View/Controller (MVC) provides an architecture that facilitates a |
73 | clean "separation of control" between the different portions of your |
74 | application. Given that many other documents cover this subject in |
75 | detail, MVC will not be discussed in depth here (for an excellent |
76 | introduction to MVC and general Catalyst concepts, please see |
865d3efb |
77 | L<Catalyst::Manual::About|Catalyst::Manual::About>). In short: |
d442cc9f |
78 | |
79 | =over 4 |
80 | |
81 | =item * Model |
82 | |
83 | The model usually represents a data store. In most applications, the |
84 | model equates to the objects that are created from and saved to your SQL |
85 | database. |
86 | |
87 | =item * View |
88 | |
89 | The view takes model objects and renders them into something for the end |
90 | user to look at. Normally this involves a template-generation tool that |
91 | creates HTML for the user's web browser, but it could easily be code |
865d3efb |
92 | that generates other forms such as PDF documents, e-mails, spreadsheets, |
93 | or even "behind the scenes" formats such as XML and JSON. |
d442cc9f |
94 | |
95 | =item * Controller |
96 | |
97 | As suggested by its name, the controller takes user requests and routes |
98 | them to the necessary model and view. |
99 | |
100 | =back |
101 | |
102 | =item * ORM |
103 | |
104 | The use of Object-Relational Mapping (ORM) technology for database |
105 | access. Specifically, ORM provides an automated and standardized means |
444d6b27 |
106 | to persist and restore objects to/from a relational database and will |
107 | automatically create our Catalyst model for use with a database. |
d442cc9f |
108 | |
109 | =back |
110 | |
111 | You can checkout the source code for this example from the catalyst |
112 | subversion repository as per the instructions in |
3ab6187c |
113 | L<Catalyst::Manual::Tutorial::01_Intro|Catalyst::Manual::Tutorial::01_Intro>. |
d442cc9f |
114 | |
3533daff |
115 | |
d442cc9f |
116 | =head1 CREATE A CATALYST PROJECT |
117 | |
3533daff |
118 | Catalyst provides a number of helper scripts that can be used to |
119 | quickly flesh out the basic structure of your application. All |
120 | Catalyst projects begin with the C<catalyst.pl> helper (see |
121 | L<Catalyst::Helper|Catalyst::Helper> for more information on helpers). |
122 | Also note that as of Catalyst 5.7000, you will not have the helper |
123 | scripts unless you install both L<Catalyst::Runtime|Catalyst::Runtime> |
124 | and L<Catalyst::Devel|Catalyst::Devel>. |
125 | |
4b4d3884 |
126 | In this first chapter of the tutorial, use the Catalyst C<catalyst.pl> |
127 | script to initialize the framework for an application called C<Hello>: |
3533daff |
128 | |
129 | $ catalyst.pl Hello |
130 | created "Hello" |
131 | created "Hello/script" |
132 | created "Hello/lib" |
133 | created "Hello/root" |
d442cc9f |
134 | ... |
3533daff |
135 | created "Hello/script/hello_create.pl" |
444d6b27 |
136 | Change to application directory and Run "perl Makefile.PL" to make sure your install is complete |
3533daff |
137 | $ cd Hello |
d442cc9f |
138 | |
444d6b27 |
139 | Note: If you are using Strawberry Perl on Win32, drop the ".pl" |
140 | from the end of the "catalyst.pl" command and simply use |
141 | "catalyst Hello". |
142 | |
d442cc9f |
143 | The C<catalyst.pl> helper script will display the names of the |
3533daff |
144 | directories and files it creates: |
145 | |
146 | Changes # Record of application changes |
865d3efb |
147 | lib # Lib directory for your app's Perl modules |
148 | Hello # Application main code directory |
3533daff |
149 | Controller # Directory for Controller modules |
150 | Model # Directory for Models |
151 | View # Directory for Views |
152 | Hello.pm # Base application module |
153 | Makefile.PL # Makefile to build application |
45d511e0 |
154 | hello.conf # Application configuration file |
3533daff |
155 | README # README file |
156 | root # Equiv of htdocs, dir for templates, css, javascript |
157 | favicon.ico |
158 | static # Directory for static files |
159 | images # Directory for image files used in welcome screen |
160 | script # Directory for Perl scripts |
161 | hello_cgi.pl # To run your app as a cgi (not recommended) |
162 | hello_create.pl # To create models, views, controllers |
163 | hello_fastcgi.pl # To run app as a fastcgi program |
164 | hello_server.pl # The normal development server |
165 | hello_test.pl # Test your app from the command line |
166 | t # Directory for tests |
167 | 01app.t # Test scaffold |
168 | 02pod.t |
169 | 03podcoverage.t |
170 | |
171 | |
172 | Catalyst will "auto-discover" modules in the Controller, Model, and |
173 | View directories. When you use the hello_create.pl script it will |
174 | create Perl module scaffolds in those directories, plus test files in |
175 | the "t" directory. The default location for templates is in the "root" |
176 | directory. The scripts in the script directory will always start with |
177 | the lowercased version of your application name. If your app is |
178 | MaiTai, then the create script would be "maitai_create.pl". |
179 | |
180 | Though it's too early for any significant celebration, we already have |
181 | a functioning application. We can use the Catalyst supplied script to |
182 | start up a development server and view the default Catalyst page in |
183 | your browser. All scripts in the script directory should be run from |
184 | the base directory of your application, so change to the Hello |
185 | directory. |
186 | |
187 | Run the following command to start up the built-in development web |
acbd7bdd |
188 | server (make sure you didn't forget the "C<cd Hello>" from the |
189 | previous step): |
d442cc9f |
190 | |
3533daff |
191 | $ script/hello_server.pl |
d442cc9f |
192 | [debug] Debug messages enabled |
865d3efb |
193 | [debug] Statistics enabled |
d442cc9f |
194 | [debug] Loaded plugins: |
195 | .----------------------------------------------------------------------------. |
f34d7f62 |
196 | | Catalyst::Plugin::ConfigLoader 0.27 | |
197 | | Catalyst::Plugin::Static::Simple 0.25 | |
d442cc9f |
198 | '----------------------------------------------------------------------------' |
199 | |
200 | [debug] Loaded dispatcher "Catalyst::Dispatcher" |
201 | [debug] Loaded engine "Catalyst::Engine::HTTP" |
3533daff |
202 | [debug] Found home "/home/me/Hello" |
e13f83cc |
203 | [debug] Loaded Config "/home/me/Hello/hello.conf" |
d442cc9f |
204 | [debug] Loaded components: |
205 | .-----------------------------------------------------------------+----------. |
206 | | Class | Type | |
207 | +-----------------------------------------------------------------+----------+ |
3533daff |
208 | | Hello::Controller::Root | instance | |
d442cc9f |
209 | '-----------------------------------------------------------------+----------' |
210 | |
211 | [debug] Loaded Private actions: |
212 | .----------------------+--------------------------------------+--------------. |
213 | | Private | Class | Method | |
214 | +----------------------+--------------------------------------+--------------+ |
3533daff |
215 | | /default | Hello::Controller::Root | default | |
216 | | /end | Hello::Controller::Root | end | |
acbd7bdd |
217 | | /index | Hello::Controller::Root | index | |
d442cc9f |
218 | '----------------------+--------------------------------------+--------------' |
219 | |
865d3efb |
220 | [debug] Loaded Path actions: |
221 | .-------------------------------------+--------------------------------------. |
222 | | Path | Private | |
223 | +-------------------------------------+--------------------------------------+ |
224 | | / | /default | |
225 | | / | /index | |
226 | '-------------------------------------+--------------------------------------' |
acbd7bdd |
227 | |
444d6b27 |
228 | [info] Hello powered by Catalyst 5.80013 |
acbd7bdd |
229 | You can connect to your server at http://debian:3000 |
d442cc9f |
230 | |
1435672d |
231 | Point your web browser to L<http://localhost:3000> (substituting a |
d442cc9f |
232 | different hostname or IP address as appropriate) and you should be |
acbd7bdd |
233 | greeted by the Catalyst welcome screen (if you get some other welcome |
234 | screen or an "Index" screen, you probably forgot to specify port 3000 |
235 | in your URL). Information similar to the following should be appended |
236 | to the logging output of the development server: |
237 | |
444d6b27 |
238 | [info] *** Request 1 (0.005/s) [20712] [Sun Oct 11 11:58:51 2009] *** |
239 | [debug] "GET" request for "/" from "172.0.0.1" |
acbd7bdd |
240 | [info] Request took 0.007342s (136.203/s) |
d442cc9f |
241 | .----------------------------------------------------------------+-----------. |
242 | | Action | Time | |
243 | +----------------------------------------------------------------+-----------+ |
acbd7bdd |
244 | | /index | 0.000491s | |
245 | | /end | 0.000595s | |
d442cc9f |
246 | '----------------------------------------------------------------+-----------' |
247 | |
248 | Press Ctrl-C to break out of the development server. |
249 | |
250 | |
3533daff |
251 | =head1 HELLO WORLD |
d442cc9f |
252 | |
3533daff |
253 | =head2 The Simplest Way |
d442cc9f |
254 | |
3533daff |
255 | The Root.pm controller is a place to put global actions that usually |
256 | execute on the root URL. Open the C<lib/Hello/Controller/Root.pm> file in |
865d3efb |
257 | your editor. You will see the "index" subroutine, which is |
3533daff |
258 | responsible for displaying the welcome screen that you just saw in |
259 | your browser. Later on you'll want to change that to something more |
865d3efb |
260 | reasonable, such as a "404" message or a redirect, but for now just |
261 | leave it alone. |
d442cc9f |
262 | |
865d3efb |
263 | sub index :Path :Args(0) { |
3533daff |
264 | my ( $self, $c ) = @_; |
865d3efb |
265 | |
266 | # Hello World |
3533daff |
267 | $c->response->body( $c->welcome_message ); |
d442cc9f |
268 | } |
269 | |
3533daff |
270 | The "C<$c>" here refers to the Catalyst context, which is used to |
271 | access the Catalyst application. In addition to many other things, |
272 | the Catalyst context provides access to "response" and "request" |
d0496197 |
273 | objects. (See L<Catalyst|Catalyst>, |
274 | L<Catalyst::Response|Catalyst::Response>, and |
275 | L<Catalyst::Request|Catalyst::Request>) |
d442cc9f |
276 | |
14e5ed66 |
277 | C<$c-E<gt>response-E<gt>body> sets the HTTP response (see |
278 | L<Catalyst::Response|Catalyst::Response>), while C<$c-E<gt>welcome_message> |
d0496197 |
279 | is a special method that returns the welcome message that you saw in |
280 | your browser. |
d442cc9f |
281 | |
444d6b27 |
282 | The ":Path :Args(0)" after the method name are attributes which |
283 | determine which URLs will be dispatched to this method. (You might see |
284 | ":Private" if you are using an older version of Catalyst, but using |
285 | that with 'default' or 'index' is currently deprecated. If so, you |
286 | should also probably upgrade before continuing the tutorial.) |
d442cc9f |
287 | |
3533daff |
288 | Some MVC frameworks handle dispatching in a central place. Catalyst, |
289 | by policy, prefers to handle URL dispatching with attributes on |
290 | controller methods. There is a lot of flexibility in specifying which |
291 | URLs to match. This particular method will match all URLs, because it |
865d3efb |
292 | doesn't specify the path (nothing comes after "Path"), but will only |
444d6b27 |
293 | accept a URL without any args because of the ":Args(0)". |
d442cc9f |
294 | |
444d6b27 |
295 | The default is to map URLs to controller names, and because of the way |
296 | that Perl handles namespaces through package names, it is simple to |
297 | create hierarchical structures in Catalyst. This means that you can |
298 | create controllers with deeply nested actions in a clean and logical |
299 | way. For example, the URL C<http://hello.com/admin/articles/create> |
300 | maps to the package C<Hello::Controller::Admin::Articles>, and the |
301 | C<create> method. |
d442cc9f |
302 | |
d0496197 |
303 | Add the following subroutine to your C<lib/Hello/Controller/Root.pm> |
304 | file: |
d442cc9f |
305 | |
3533daff |
306 | sub hello : Global { |
307 | my ( $self, $c ) = @_; |
d0496197 |
308 | |
3533daff |
309 | $c->response->body("Hello, World!"); |
310 | } |
d442cc9f |
311 | |
acbd7bdd |
312 | B<TIP>: See Appendix 1 for tips on removing the leading spaces when |
313 | cutting and pasting example code from POD-based documents. |
314 | |
3533daff |
315 | Here you're sending your own string to the webpage. |
316 | |
317 | Save the file, start the server (stop and restart it if it's still |
444d6b27 |
318 | running), and go to L<http://localhost:3000/hello> to |
319 | see "Hello, World!" Also notice that a new action is listed under |
320 | "Loaded Private actions" in the development server debug output. |
3533daff |
321 | |
865d3efb |
322 | |
3533daff |
323 | =head2 Hello, World! Using a View and a Template |
324 | |
444d6b27 |
325 | In the Catalyst world a "View" itself is not a page of XHTML or a |
326 | template designed to present a page to a browser. Rather, it is the |
327 | module that determines the I<type> of view -- HTML, pdf, XML, etc. For |
328 | the thing that generates the I<content> of that view (such as the a |
329 | Toolkit Template template file), the actual templates go under the |
865d3efb |
330 | "root" directory. |
3533daff |
331 | |
332 | To create a TT view, run: |
333 | |
334 | $ script/hello_create.pl view TT TT |
335 | |
336 | This creates the C<lib/Hello/View/TT.pm> module, which is a subclass of |
1435672d |
337 | C<Catalyst::View::TT>. |
338 | |
339 | =over 4 |
340 | |
341 | =item * |
342 | |
343 | The "view" keyword tells the create script that you are creating a view. |
344 | |
345 | =item * |
346 | |
347 | The first "TT" tells the script to name the View module "TT.pm", which is a |
348 | commonly used name for TT views. (You can name it anything you want, such as |
349 | "HTML.pm".) |
350 | |
351 | =item * |
352 | |
444d6b27 |
353 | The final "TT" tells Catalyst the I<type> of the view, with "TT" |
354 | indicating that you want to a Template Toolkit view. |
1435672d |
355 | |
356 | =back |
357 | |
444d6b27 |
358 | If you look at C<lib/Hello/View/TT.pm> you will find that it only |
359 | contains a config statement to set the TT extension to ".tt". |
3533daff |
360 | |
361 | Now that the TT.pm "View" exists, Catalyst will autodiscover it and be |
444d6b27 |
362 | able to use it to display the view templates using the "process" |
3533daff |
363 | method that it inherits from the C<Catalyst::View::TT class>. |
364 | |
c010ae0d |
365 | Template Toolkit is a very full featured template facility, with |
865d3efb |
366 | excellent documentation at L<http://template-toolkit.org/>, |
3533daff |
367 | but since this is not a TT tutorial, we'll stick to only basic TT |
368 | usage here (and explore some of the more common TT features in later |
4b4d3884 |
369 | chapters of the tutorial). |
3533daff |
370 | |
371 | Create a C<root/hello.tt> template file (put it in the C<root> under |
372 | the C<Hello> directory that is the base of your application). Here is |
373 | a simple sample: |
374 | |
3533daff |
375 | <p> |
1435672d |
376 | This is a TT view template, called '[% template.name %]'. |
3533daff |
377 | </p> |
378 | |
379 | [% and %] are markers for the TT parts of the template. Inside you can |
1435672d |
380 | access Perl variables and classes, and use TT directives. In this |
381 | case, we're using a special TT variable that defines the name of the |
382 | template file (C<hello.tt>). The rest of the template is normal HTML. |
383 | |
384 | Change the hello method in C<lib/Hello/Controller/Root.pm> to the |
385 | following: |
3533daff |
386 | |
387 | sub hello : Global { |
388 | my ( $self, $c ) = @_; |
d0496197 |
389 | |
3533daff |
390 | $c->stash->{template} = 'hello.tt'; |
391 | } |
d442cc9f |
392 | |
444d6b27 |
393 | This time, instead of doing C<$c-E<gt>response-E<gt>body()>, you are |
394 | setting the value of the "template" hash key in the Catalyst "stash", |
395 | an area for putting information to share with other parts of your |
396 | application. The "template" key determines which template will be |
397 | displayed at the end of the request cycle. Catalyst controllers have a |
398 | default "end" action for all methods which causes the first (or |
399 | default) view to be rendered (unless there's a C<$c-E<gt>response- |
400 | E<gt>body()> statement). So your template will be magically displayed |
401 | at the end of your method. |
d442cc9f |
402 | |
3533daff |
403 | After saving the file, restart the development server, and look at |
d0496197 |
404 | L<http://localhost:3000/hello> again. You should |
3533daff |
405 | see the template that you just made. |
d442cc9f |
406 | |
d442cc9f |
407 | |
3533daff |
408 | =head1 CREATE A SIMPLE CONTROLLER AND AN ACTION |
d442cc9f |
409 | |
3533daff |
410 | Create a controller named "Site" by executing the create script: |
d442cc9f |
411 | |
3533daff |
412 | $ script/hello_create.pl controller Site |
d442cc9f |
413 | |
3533daff |
414 | This will create a C<lib/Hello/Controller/Site.pm> file (and a test |
415 | file). Bring Site.pm up in your editor, and you can see that there's |
444d6b27 |
416 | not much there. |
d442cc9f |
417 | |
d0496197 |
418 | In C<lib/Hello/Controller/Site.pm>, add the following method: |
d442cc9f |
419 | |
3533daff |
420 | sub test : Local { |
421 | my ( $self, $c ) = @_; |
d0496197 |
422 | |
3533daff |
423 | $c->stash->{username} = "John"; |
424 | $c->stash->{template} = 'site/test.tt'; |
d442cc9f |
425 | } |
426 | |
1435672d |
427 | Notice the "Local" attribute on the C<test> method. This will cause |
444d6b27 |
428 | the C<test> action (now that we have assigned an "action type" to the |
429 | method it appears as a "controller action" to Catalyst) to be executed |
1435672d |
430 | on the "controller/method" URL, or, in this case, "site/test". We |
431 | will see additional information on controller actions throughout the |
432 | rest of the tutorial, but if you are curious take a look at |
433 | L<Catalyst::Manual::Intro/Actions>. |
434 | |
435 | It's not actually necessary to set the template value as we do here. |
436 | By default TT will attempt to render a template that follows the |
437 | naming pattern "controller/method.tt", and we're following that |
438 | pattern here. However, in other situations you will need to specify |
439 | the template (such as if you've "forwarded" to the method, or if it |
440 | doesn't follow the default naming convention). |
441 | |
442 | We've also put the variable "username" into the stash, for use in the |
443 | template. |
d442cc9f |
444 | |
3533daff |
445 | Make a subdirectory "site" in the "root" directory. Copy the hello.tt |
d0496197 |
446 | file into the directory as C<root/site/test.tt>, or create a new |
447 | template file at that location. Include a line like: |
d442cc9f |
448 | |
d0496197 |
449 | <p>Hello, [% username %]!</p> |
d442cc9f |
450 | |
3533daff |
451 | Bring up or restart the server. Notice in the server output that |
452 | C</site/test> is listed in the Loaded Path actions. Go to |
865d3efb |
453 | L<http://localhost:3000/site/test> in your browser. |
d442cc9f |
454 | |
3533daff |
455 | You should see your test.tt file displayed, including the name "John" |
456 | that you set in the controller. |
d442cc9f |
457 | |
d442cc9f |
458 | |
3533daff |
459 | =head1 AUTHORS |
d442cc9f |
460 | |
3533daff |
461 | Gerda Shank, C<gerda.shank@gmail.com> |
d442cc9f |
462 | Kennedy Clark, C<hkclark@gmail.com> |
463 | |
464 | Please report any errors, issues or suggestions to the author. The |
465 | most recent version of the Catalyst Tutorial can be found at |
59884771 |
466 | L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Tutorial/>. |
d442cc9f |
467 | |
45c7830f |
468 | Copyright 2006-2008, Kennedy Clark & Gerda Shank, under Creative Commons License |
865d3efb |
469 | (L<http://creativecommons.org/licenses/by-sa/3.0/us/>). |