Revision history for Catalyst-Manual
+ - Change from the use of "part" to refer to each .pod file for the
+ tutorial in favor of the more intuitive word "chapter." "Part"
+ was just to ambiguous (e.g., does "prior part" refer to the prior
+ .pod file or the prior section in the current .pod file).
+ - Fix typos
+
5.7018 8 Mar 2009
- Add a new section to BasicCRUD covering more advanced features of
DBIC ("EXPLORING THE POWER OF DBIC")
=back
-Final code tarballs for each part of the tutorial are available at
+Final code tarballs for each chapter of the tutorial are available at
L<http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/Tutorial/>.
=head1 Detailed Table of Contents
-=head2 L<Part 1: Introduction|Catalyst::Manual::Tutorial::Intro>
+=head2 L<Chapter 1: Intro|Catalyst::Manual::Tutorial::Intro>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 2: Catalyst Basics|Catalyst::Manual::Tutorial::CatalystBasics>
+=head2 L<Chapter 2: Catalyst Basics|Catalyst::Manual::Tutorial::CatalystBasics>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 3: More Catalyst Basics|Catalyst::Manual::Tutorial::MoreCatalystBasics>
+=head2 L<Chapter 3: More Catalyst Basics|Catalyst::Manual::Tutorial::MoreCatalystBasics>
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 4: Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD>
+=head2 L<Chapter 4: Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 5: Authentication|Catalyst::Manual::Tutorial::Authentication>
+=head2 L<Chapter 5: Authentication|Catalyst::Manual::Tutorial::Authentication>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 6: Authorization|Catalyst::Manual::Tutorial::Authorization>
+=head2 L<Chapter 6: Authorization|Catalyst::Manual::Tutorial::Authorization>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 7: Debugging|Catalyst::Manual::Tutorial::Debugging>
+=head2 L<Chapter 7: Debugging|Catalyst::Manual::Tutorial::Debugging>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 8: Testing|Catalyst::Manual::Tutorial::Testing>
+=head2 L<Chapter 8: Testing|Catalyst::Manual::Tutorial::Testing>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 9: Advanced CRUD|Catalyst::Manual::Tutorial::AdvancedCRUD>
+=head2 L<Chapter 9: Advanced CRUD|Catalyst::Manual::Tutorial::AdvancedCRUD>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=back
-=head2 L<Part 10: Appendices|Catalyst::Manual::Tutorial::Appendices>
+=head2 L<Chapter 10: Appendices|Catalyst::Manual::Tutorial::Appendices>
+
+Note: Click on the heading in the previous line to jump to the actual
+chapter. Below is a "table of contents" for this chapter.
=over 4
=head1 NAME
-Catalyst::Manual::Tutorial::AdvancedCRUD - Catalyst Tutorial - Part 9: Advanced CRUD
+Catalyst::Manual::Tutorial::AdvancedCRUD - Catalyst Tutorial - Chapter 9: Advanced CRUD
=head1 OVERVIEW
-This is B<Part 9 of 10> for the Catalyst tutorial.
+This is B<Chapter 9 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial explores more advanced functionality for
-Create, Read, Update, and Delete (CRUD) than we saw in Part 4. In
+This chapter of the tutorial explores more advanced functionality for
+Create, Read, Update, and Delete (CRUD) than we saw in Chapter 4. In
particular, it looks at a number of techniques that can be useful for
the Update portion of CRUD, such as automated form generation,
validation of user-entered data, and automated transfer of data between
=head1 NAME
-Catalyst::Manual::Tutorial::AdvancedCRUD::FormBuilder - Catalyst Tutorial - Part 9: Advanced CRUD - FormBuilder
+Catalyst::Manual::Tutorial::AdvancedCRUD::FormBuilder - Catalyst Tutorial - Chapter 9: Advanced CRUD - FormBuilder
-NOTE: This part of the tutorial is in progress. Feel free to volunteer to help out. :-)
+NOTE: This chapter of the tutorial is in progress. Feel free to
+volunteer to help out. :-)
=head1 OVERVIEW
-This is B<Part 9 of 10> for the Catalyst tutorial.
+This is B<Chapter 9 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 NAME
-
-
-Catalyst::Manual::Tutorial::AdvancedCRUD::FormFu - Catalyst Tutorial - Part 9: Advanced CRUD - FormFu
+Catalyst::Manual::Tutorial::AdvancedCRUD::FormFu - Catalyst Tutorial - Chapter 9: Advanced CRUD - FormFu
=head1 OVERVIEW
-This is B<Part 9 of 10> for the Catalyst tutorial.
+This is B<Chapter 9 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 C<HTML::FormFu> FORM CREATION
This section looks at how L<HTML::FormFu|HTML::FormFu> can be used to
-add additional functionality to the manually created form from Part 4.
+add additional functionality to the manually created form from Chapter 4.
=head2 Inherit From C<Catalyst::Controller::HTML::FormFu>
=head1 NAME
-Catalyst::Manual::Tutorial::Appendices - Catalyst Tutorial - Part 10: Appendices
+Catalyst::Manual::Tutorial::Appendices - Catalyst Tutorial - Chapter 10: Appendices
=head1 OVERVIEW
-This is B<Part 10 of 10> for the Catalyst tutorial.
+This is B<Chapter 10 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial provides supporting information relevant to
+This chapter of the tutorial provides supporting information relevant to
the Catalyst tutorial.
=item *
-Part 2: Catalyst Basics
+Chapter 2: Catalyst Basics
=over 4
=item *
-Part 4: Authentication
+Chapter 4: Authentication
=over 4
=item *
-Part 2: Catalyst Basics
+Chapter 2: Catalyst Basics
=over 4
=item *
-Part 4: Authentication
+Chapter 4: Authentication
=over 4
=head1 NAME
-Catalyst::Manual::Tutorial::Authentication - Catalyst Tutorial - Part 5: Authentication
+Catalyst::Manual::Tutorial::Authentication - Catalyst Tutorial - Chapter 5: Authentication
=head1 OVERVIEW
-This is B<Part 5 of 10> for the Catalyst tutorial.
+This is B<Chapter 5 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
Now that we finally have a simple yet functional application, we can
focus on providing authentication (with authorization coming next in
-Part 6).
+Chapter 6).
-This part of the tutorial is divided into two main sections: 1) basic,
+This chapter of the tutorial is divided into two main sections: 1) basic,
cleartext authentication and 2) hash-based authentication.
You can checkout the source code for this example from the catalyst
First, we add both user and role information to the database (we will
add the role information here although it will not be used until the
-authorization section, Part 6). Create a new SQL script file by opening
+authorization section, Chapter 6). Create a new SQL script file by opening
C<myapp02.sql> in your editor and insert:
--
The code for these three sets of updates is obviously very similar to
the edits we made to the C<Books>, C<Authors>, and C<BookAuthors>
-classes created in Part 3.
+classes created in Chapter 3.
Note that we do not need to make any change to the
C<lib/MyApp/Schema.pm> schema file. It simply tells DBIC to load all
into C<MyApp-E<gt>config> using the
L<ConfigLoader|Catalyst::Plugin::ConfigLoader> plugin.
-As discussed in Part 3 of the tutorial, Catalyst has recently
+As discussed in Chapter 3 of the tutorial, Catalyst has recently
switched from a default config file format of YAML to
L<Config::General|Config::General> (an apache-like format). In case
you are using a version of Catalyst earlier than v5.7014, delete the
=head1 USING THE SESSION FOR FLASH
-As discussed in the previous part of the tutorial, C<flash> allows you to
-set variables in a way that is very similar to C<stash>, but it will
-remain set across multiple requests. Once the value is read, it
-is cleared (unless reset). Although C<flash> has nothing to do with
-authentication, it does leverage the same session plugins. Now that
-those plugins are enabled, let's go back and update the "delete
-and redirect with query parameters" code seen at the end of the
-L<Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD> part of the
-tutorial to take advantage of C<flash>.
+As discussed in the previous chapter of the tutorial, C<flash> allows
+you to set variables in a way that is very similar to C<stash>, but it
+will remain set across multiple requests. Once the value is read, it
+is cleared (unless reset). Although C<flash> has nothing to do with
+authentication, it does leverage the same session plugins. Now that
+those plugins are enabled, let's go back and update the "delete and
+redirect with query parameters" code seen at the end of the L<Basic
+CRUD|Catalyst::Manual::Tutorial::BasicCRUD> chapter of the tutorial to
+take advantage of C<flash>.
First, open C<lib/MyApp/Controller/Books.pm> and modify C<sub delete>
to match the following (everything after the model search line of code
=head1 NAME
-Catalyst::Manual::Tutorial::Authorization - Catalyst Tutorial - Part 6: Authorization
+Catalyst::Manual::Tutorial::Authorization - Catalyst Tutorial - Chapter 6: Authorization
=head1 OVERVIEW
-This is B<Part 6 of 10> for the Catalyst tutorial.
+This is B<Chapter 6 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial adds role-based authorization to the
-existing authentication implemented in Part 5. It provides simple
+This chapter of the tutorial adds role-based authorization to the
+existing authentication implemented in Chapter 5. It provides simple
examples of how to use roles in both TT templates and controller
actions. The first half looks at basic authorization concepts. The
second half looks at how moving your authorization code to your model
body has already been set. In reality you would probably want to use a
technique that maintains the visual continuity of your template layout
(for example, using the "status" or "error" message feature added in
-Part 3 or C<detach> to an action that shows an "unauthorized" page).
+Chapter 3 or C<detach> to an action that shows an "unauthorized" page).
B<TIP>: If you want to keep your existing C<url_create> method, you can
create a new copy and comment out the original by making it look like a
=head1 NAME
-Catalyst::Manual::Tutorial::BasicCRUD - Catalyst Tutorial - Part 4: Basic CRUD
+Catalyst::Manual::Tutorial::BasicCRUD - Catalyst Tutorial - Chapter 4: Basic CRUD
=head1 OVERVIEW
-This is B<Part 4 of 10> for the Catalyst tutorial.
+This is B<Chapter 4 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial builds on the fairly primitive application
-created in Part 3 to add basic support for Create, Read, Update, and
-Delete (CRUD) of C<Book> objects. Note that the 'list' function in Part
-2 already implements the Read portion of CRUD (although Read normally
-refers to reading a single object; you could implement full read
-functionality using the techniques introduced below). This section will
-focus on the Create and Delete aspects of CRUD. More advanced
-capabilities, including full Update functionality, will be addressed in
-Part 9.
-
-Although this part of the tutorial will show you how to build CRUD
-functionality yourself, another option is to use a "CRUD builder" type
-of tool to automate the process. You get less control, but it's quick
-and easy. For example, see
-L<CatalystX::ListFramework::Builder|CatalystX::ListFramework::Builder>,
-L<CatalystX::CRUD|CatalystX::CRUD>, and
+This chapter of the tutorial builds on the fairly primitive
+application created in Chapter 3 to add basic support for Create,
+Read, Update, and Delete (CRUD) of C<Book> objects. Note that the
+'list' function in Chapter 2 already implements the Read portion of
+CRUD (although Read normally refers to reading a single object; you
+could implement full read functionality using the techniques
+introduced below). This section will focus on the Create and Delete
+aspects of CRUD. More advanced capabilities, including full Update
+functionality, will be addressed in Chapter 9.
+
+Although this chapter of the tutorial will show you how to build CRUD
+functionality yourself, another option is to use a "CRUD builder" type
+of tool to automate the process. You get less control, but it's quick
+and easy. For example, see
+L<CatalystX::ListFramework::Builder|CatalystX::ListFramework::Builder>,
+L<CatalystX::CRUD|CatalystX::CRUD>, and
L<CatalystX::CRUD::YUI|CatalystX::CRUD::YUI>.
You can checkout the source code for this example from the catalyst
to the base TT capabilities. Here, the plugin allows
L<Data::Dumper|Data::Dumper> "pretty printing" of objects and
variables. Other than that, the rest of the code should be familiar
-from the examples in Part 3.
+from the examples in Chapter 3.
=head2 Try the C<url_create> Feature
=head1 CONVERT TO A CHAINED ACTION
Although the example above uses the same C<Local> action type for the
-method that we saw in the previous part of the tutorial, there is an
+method that we saw in the previous chapter of the tutorial, there is an
alternate approach that allows us to be more specific while also
paving the way for more advanced capabilities. Change the method
declaration for C<url_create> in C<lib/MyApp/Controller/Books.pm> you
As we will see shortly, a chain can consist of as many "links" as you
wish, with each part capturing some arguments and doing some work
along the way. We will continue to use the Chained action type in this
-part of the tutorial and explore slightly more advanced capabilities
+chapter of the tutorial and explore slightly more advanced capabilities
with the base method and delete feature below. But Chained dispatch
is capable of far more. For additional information, see
L<Catalyst::Manual::Intro/Action types>,
B<Note:> Having the user enter the primary key ID for the author is
obviously crude; we will address this concern with a drop-down list in
-Part 9.
+Chapter 9.
=head1 A SIMPLE DELETE FEATURE
=head2 Using C<uri_for> to Pass Query Parameters
-There are several ways to pass information across a redirect. One
-option is to use the C<flash> technique that we will see in Part 5 of
-the tutorial; however, here we will pass the information via query
-parameters on the redirect itself. Open
-C<lib/MyApp/Controller/Books.pm> and update the existing C<sub delete>
+There are several ways to pass information across a redirect. One
+option is to use the C<flash> technique that we will see in Chapter 5
+of the tutorial; however, here we will pass the information via query
+parameters on the redirect itself. Open
+C<lib/MyApp/Controller/Books.pm> and update the existing C<sub delete>
method to match the following:
=head2 delete
B<NOTE:> Another popular method for maintaining server-side
information across a redirect is to use the C<flash> technique we
-discuss in the next part of the tutorial,
+discuss in the next chapter of the tutorial,
L<Authentication|Catalyst::Manual::Tutorial::Authentication>. While
C<flash> is a "slicker" mechanism in that it's all handled by the
server and doesn't "pollute" your URLs, B<it is important to note that
the newer C<load_namespaces> feature, DBIC automatically looks for
your Result Class files in a subdirectory of the Schema directory
called C<Result> (the files in C<lib/MyApp/Schema> were already there
-from Part 3 of the tutorial; the files in C<lib/MyApp/Schema/Result>
+from Chapter 3 of the tutorial; the files in C<lib/MyApp/Schema/Result>
are new).
If you are using SQLite, you will need to manually re-enter the
-relationship configuration as we did in Part 3 of the tutorial (if you
+relationship configuration as we did in Chapter 3 of the tutorial (if you
are using different database, the relationships might have been auto-
generated by Schema::Loader). One option is to use the following
command-line perl script to migrate the information across
=head1 NAME
-Catalyst::Manual::Tutorial::CatalystBasics - Catalyst Tutorial - Part 2: Catalyst Application Development Basics
+Catalyst::Manual::Tutorial::CatalystBasics - Catalyst Tutorial - Chapter 2: Catalyst Application Development Basics
=head1 OVERVIEW
-This is B<Part 2 of 10> for the Catalyst tutorial.
+This is B<Chapter 2 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-In this part of the tutorial, we will create a very basic Catalyst web
-application, demonstrating a number of powerful capabilities, such as:
+In this chapter of the tutorial, we will create a very basic Catalyst
+web application, demonstrating a number of powerful capabilities, such
+as:
=over 4
scripts unless you install both L<Catalyst::Runtime|Catalyst::Runtime>
and L<Catalyst::Devel|Catalyst::Devel>.
-In this first part of the tutorial, use the Catalyst
-C<catalyst.pl> script to initialize the framework for an
-application called C<Hello>:
+In this first chapter of the tutorial, use the Catalyst C<catalyst.pl>
+script to initialize the framework for an application called C<Hello>:
$ catalyst.pl Hello
created "Hello"
excellent documentation at L<http://template-toolkit.org/>,
but since this is not a TT tutorial, we'll stick to only basic TT
usage here (and explore some of the more common TT features in later
-parts of the tutorial).
+chapters of the tutorial).
Create a C<root/hello.tt> template file (put it in the C<root> under
the C<Hello> directory that is the base of your application). Here is
=head1 NAME
-Catalyst::Manual::Tutorial::Debugging - Catalyst Tutorial - Part 7: Debugging
+Catalyst::Manual::Tutorial::Debugging - Catalyst Tutorial - Chapter 7: Debugging
=head1 OVERVIEW
-This is B<Part 7 of 10> for the Catalyst tutorial.
+This is B<Chapter 7 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial takes a brief look at the primary options
+This chapter of the tutorial takes a brief look at the primary options
available for troubleshooting Catalyst applications.
Note that when it comes to debugging and troubleshooting, there are two
=head1 NAME
-Catalyst::Manual::Tutorial::Intro - Catalyst Tutorial - Part 1: Introduction
+Catalyst::Manual::Tutorial::Intro - Catalyst Tutorial - Chapter 1: Introduction
=head1 OVERVIEW
-This is B<Part 1 of 10> for the Catalyst tutorial.
+This is B<Chapter 1 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
svn co http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/Tutorial/ CatalystTutorial
-This will download the most recent tarball for each part of the
+This will download the most recent tarball for each chapter of the
tutorial into the CatalystTutorial directory on your machine.
B<These reference implementations are provided so that when you follow
=head1 WHERE TO GET WORKING CODE
-Each part of the tutorial has complete code available as a tarball in
+Each chapter of the tutorial has complete code available as a tarball in
the main Catalyst Subversion repository (see the note at the beginning
of each part for the appropriate svn command to use).
-B<NOTE:> You can run the test cases for the final code through Part 8
+B<NOTE:> You can run the test cases for the final code through Chapter 8
with the following commands:
sudo cpan Catalyst::Model::DBIC::Schema Time::Warp DBICx::TestDatabase \
DBIx::Class::DynamicDefault DBIx::Class::TimeStamp
- wget http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/Tutorial/MyApp_Part8.tgz
- tar zxvf MyApp_Part8.tgz
+ wget http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/Tutorial/MyApp_Chapter8.tgz
+ tar zxvf MyApp_Chapter8.tgz
cd MyApp
CATALYST_DEBUG=0 prove --lib lib t
If you wish to include the L<HTML::FormFu|HTML::FormFu> section in
-your tests, substitute C<MyApp_Part9_FormFu.tgz> for
-C<MyApp_Part8.tgz> in the URL above. However, you will also need to
+your tests, substitute C<MyApp_Chapter9_FormFu.tgz> for
+C<MyApp_Chapter8.tgz> in the URL above. However, you will also need to
run the following additional commands:
sudo aptitude -y install libhtml-formfu-perl libmoose-perl \
earlier, change C<localhost> to a different IP address or DNS name if
you are running your web browser and your Catalyst development on
different boxes). We will obviously see more about how to use the
-application as we go through the remaining parts of the tutorial, but
+application as we go through the remaining chapters of the tutorial, but
for now you can log in using the username "test01" and a password of
"mypass".
=head1 NAME
-Catalyst::Manual::Tutorial::MoreCatalystBasics - Catalyst Tutorial - Part 3: More Catalyst Application Development Basics
+Catalyst::Manual::Tutorial::MoreCatalystBasics - Catalyst Tutorial - Chapter 3: More Catalyst Application Development Basics
=head1 OVERVIEW
-This is B<Part 3 of 10> for the Catalyst tutorial.
+This is B<Chapter 3 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-This part of the tutorial builds on the work done in Part 2 to explore
-some features that are more typical of "real world" web applications.
-From this part of the tutorial onward, we will be building a simple
-book database application. Although the application will be too
-limited to be of use to anyone, it should provide a basic environment
-where we can explore a variety of features used in virtually all web
-applications.
+This chapter of the tutorial builds on the work done in Chapter 2 to
+explore some features that are more typical of "real world" web
+applications. From this chapter of the tutorial onward, we will be
+building a simple book database application. Although the application
+will be too limited to be of use to anyone, it should provide a basic
+environment where we can explore a variety of features used in
+virtually all web applications.
You can checkout the source code for this example from the catalyst
subversion repository as per the instructions in
The remainder of the tutorial will build an application called C<MyApp>.
First use the Catalyst C<catalyst.pl> script to initialize the framework
for the C<MyApp> application (make sure you aren't still inside the
-directory of the C<Hello> application from the previous part of the
+directory of the C<Hello> application from the previous chapter of the
tutorial or in a directory that already has a "MyApp" subdirectory):
$ catalyst.pl MyApp
created "MyApp/script/myapp_create.pl"
$ cd MyApp
-This creates a similar skeletal structure to what we saw in Part 2 of
+This creates a similar skeletal structure to what we saw in Chapter 2 of
the tutorial, except with C<MyApp> and C<myapp> substituted for
C<Hello> and C<hello>.
hard-coded inside your Perl modules). Config::General uses syntax
very similar to Apache configuration files. We will see how to use
this feature of Catalyst during the authentication and authorization
-sections (Part 5 and Part 6).
+sections (Chapter 5 and Chapter 6).
B<IMPORTANT NOTE:> If you are using a version of
L<Catalyst::Devel|Catalyst::Devel> prior to version 1.06, be aware
created "/home/me/MyApp/script/../lib/MyApp/Controller/Books.pm"
created "/home/me/MyApp/script/../t/controller_Books.t"
-Then edit C<lib/MyApp/Controller/Books.pm> (as discussed in Part 2 of
+Then edit C<lib/MyApp/Controller/Books.pm> (as discussed in Chapter 2 of
the Tutorial, Catalyst has a separate directory under C<lib/MyApp> for
each of the three parts of MVC: C<Model>, C<View>, and C<Controller>)
and add the following method to the controller:
=head1 CATALYST VIEWS
-As mentioned in Part 2 of the tutorial, views are where you render
+As mentioned in Chapter 2 of the tutorial, views are where you render
output, typically for display in the user's web browser (but also
possibly using other display output-generation systems). The code in
C<lib/MyApp/View> selects the I<type> of view to use, with the actual
Both helpers are similar. C<TT> creates the C<lib/MyApp/View/TT.pm>
file and leaves the creation of any hierarchical template organization
entirely up to you. (It also creates a C<t/view_TT.t> file for testing;
-test cases will be discussed in Part 8.) C<TTSite>, on the other hand,
+test cases will be discussed in Chapter 8.) C<TTSite>, on the other hand,
creates a modular and hierarchical view layout with
separate Template Toolkit (TT) files for common header and footer
information, configuration values, a CSS stylesheet, and more.
The Catalyst stash only lasts for a single HTTP request. If
you need to retain information across requests you can use
L<Catalyst::Plugin::Session|Catalyst::Plugin::Session> (we will use
-Catalyst sessions in the Authentication part of the tutorial).
+Catalyst sessions in the Authentication chapter of the tutorial).
=item *
C<load_namspaces> technique. For new applications, please try to use
C<load_namespaces> since it more easily supports a very useful DBIC
technique called "ResultSet Classes." We will migrate to
-C<load_namespaces> in Part 4 (BasicCRUD) of this tutorial.
+C<load_namespaces> in Chapter 4 (BasicCRUD) of this tutorial.
=head2 Updating the Generated DBIC Schema Files
=head1 OPTIONAL INFORMATION
-B<NOTE: The rest of this part of the tutorial is optional. You can
-skip to Part 4, L<Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD>,
+B<NOTE: The rest of this chapter of the tutorial is optional. You can
+skip to Chapter 4, L<Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD>,
if you wish.>
B<NOTE:> Please note that if you use the default template technique,
you will B<not> be able to use either the C<$c-E<gt>forward> or
-the C<$c-E<gt>detach> mechanisms (these are discussed in Part 2 and
-Part 9 of the Tutorial).
+the C<$c-E<gt>detach> mechanisms (these are discussed in Chapter 2 and
+Chapter 9 of the Tutorial).
=head2 Return To A Manually-Specified Template
=head1 NAME
-Catalyst::Manual::Tutorial::Testing - Catalyst Tutorial - Part 8: Testing
+Catalyst::Manual::Tutorial::Testing - Catalyst Tutorial - Chapter 8: Testing
=head1 OVERVIEW
-This is B<Part 8 of 10> for the Catalyst tutorial.
+This is B<Chapter 8 of 10> for the Catalyst tutorial.
L<Tutorial Overview|Catalyst::Manual::Tutorial>
=head1 DESCRIPTION
-You may have noticed that the Catalyst Helper scripts automatically
-create basic C<.t> test scripts under the C<t> directory. This part of
-the tutorial briefly looks at how these tests can be used to not only
-ensure that your application is working correctly at the present time,
-but also provide automated regression testing as you upgrade various
-pieces of your application over time.
+You may have noticed that the Catalyst Helper scripts automatically
+create basic C<.t> test scripts under the C<t> directory. This
+chapter of the tutorial briefly looks at how these tests can be used
+to not only ensure that your application is working correctly at the
+present time, but also provide automated regression testing as you
+upgrade various pieces of your application over time.
You can checkout the source code for this example from the catalyst
subversion repository as per the instructions in
$ DBIC_TRACE=0 CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t
-Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG>
-and C<-v> settings. If you find that there are errors, use the
-techniques discussed in the "Catalyst Debugging" section (Part 7) to
-isolate and fix any problems.
+Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG> and C<-v>
+settings. If you find that there are errors, use the techniques
+discussed in the "Catalyst Debugging" section (Chapter 7) to isolate
+and fix any problems.
If you want to run the test case under the Perl interactive debugger,
try a command such as:
projects / catagits/Catalyst-Manual.git / commitdiff