From: Kennedy Clark Date: Tue, 10 Mar 2009 21:38:26 +0000 (+0000) Subject: Change from the use of "part" to refer to each .pod file for the tutorial in favor... X-Git-Tag: v5.8005~182 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=commitdiff_plain;h=4b4d38842b2383a70a54bcadb493505950b469dd Change from the use of "part" to refer to each .pod file for the tutorial in favor of the more intuitive word "chapter." --- diff --git a/Changes b/Changes index 5d1fb6c..f6da7d5 100644 --- a/Changes +++ b/Changes @@ -1,5 +1,11 @@ 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") diff --git a/lib/Catalyst/Manual/Tutorial.pod b/lib/Catalyst/Manual/Tutorial.pod index 38c6145..96caa8a 100644 --- a/lib/Catalyst/Manual/Tutorial.pod +++ b/lib/Catalyst/Manual/Tutorial.pod @@ -58,14 +58,17 @@ L =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. =head1 Detailed Table of Contents -=head2 L +=head2 L + +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 @@ -88,7 +91,10 @@ WHERE TO GET WORKING CODE =back -=head2 L +=head2 L + +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 @@ -119,8 +125,10 @@ CREATE A SIMPLE CONTROLLER AND AN ACTION =back -=head2 L +=head2 L +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 @@ -224,7 +232,10 @@ Return To A Manually-Specified Template =back -=head2 L +=head2 L + +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 @@ -311,7 +322,10 @@ Try the Delete and Redirect With Query Param Logic =back -=head2 L +=head2 L + +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 @@ -406,7 +420,10 @@ Switch To Flash-To-Stash =back -=head2 L +=head2 L + +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 @@ -461,7 +478,10 @@ Add a Method to Handle Access Violations =back -=head2 L +=head2 L + +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 @@ -480,7 +500,10 @@ DEBUGGING MODULES FROM CPAN =back -=head2 L +=head2 L + +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 @@ -503,7 +526,10 @@ SUPPORTING BOTH PRODUCTION AND TEST DATABASES =back -=head2 L +=head2 L + +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 @@ -514,7 +540,10 @@ ADVANCED CRUD OPTIONS =back -=head2 L +=head2 L + +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 diff --git a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod index e0a678b..5b6b388 100644 --- a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod +++ b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,8 +56,8 @@ L =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 diff --git a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormBuilder.pod b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormBuilder.pod index d005c0f..b997e8b 100644 --- a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormBuilder.pod +++ b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormBuilder.pod @@ -1,12 +1,13 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L diff --git a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormFu.pod b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormFu.pod index be90d17..f261950 100644 --- a/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormFu.pod +++ b/lib/Catalyst/Manual/Tutorial/AdvancedCRUD/FormFu.pod @@ -1,13 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -96,7 +94,7 @@ that aren't available as Debian packages: =head1 C FORM CREATION This section looks at how L 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 diff --git a/lib/Catalyst/Manual/Tutorial/Appendices.pod b/lib/Catalyst/Manual/Tutorial/Appendices.pod index c8037df..fe5606e 100644 --- a/lib/Catalyst/Manual/Tutorial/Appendices.pod +++ b/lib/Catalyst/Manual/Tutorial/Appendices.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,7 +56,7 @@ B =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. @@ -153,7 +153,7 @@ Howard for the help. =item * -Part 2: Catalyst Basics +Chapter 2: Catalyst Basics =over 4 @@ -330,7 +330,7 @@ Regenerate the model using the Catalyst "_create.pl" script: =item * -Part 4: Authentication +Chapter 4: Authentication =over 4 @@ -413,7 +413,7 @@ Tom Lanyon. =item * -Part 2: Catalyst Basics +Chapter 2: Catalyst Basics =over 4 @@ -606,7 +606,7 @@ Generate the model using the Catalyst "_create.pl" script: =item * -Part 4: Authentication +Chapter 4: Authentication =over 4 diff --git a/lib/Catalyst/Manual/Tutorial/Authentication.pod b/lib/Catalyst/Manual/Tutorial/Authentication.pod index aa77c9c..42a300c 100644 --- a/lib/Catalyst/Manual/Tutorial/Authentication.pod +++ b/lib/Catalyst/Manual/Tutorial/Authentication.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -58,9 +58,9 @@ L 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 @@ -78,7 +78,7 @@ application. 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 in your editor and insert: -- @@ -208,7 +208,7 @@ C: The code for these three sets of updates is obviously very similar to the edits we made to the C, C, and C -classes created in Part 3. +classes created in Chapter 3. Note that we do not need to make any change to the C schema file. It simply tells DBIC to load all @@ -302,7 +302,7 @@ information in C and automatically load this information into Cconfig> using the L 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 (an apache-like format). In case you are using a version of Catalyst earlier than v5.7014, delete the @@ -747,15 +747,15 @@ login as before. When done, click the "logout" link on the login page =head1 USING THE SESSION FOR FLASH -As discussed in the previous part of the tutorial, C allows you to -set variables in a way that is very similar to C, but it will -remain set across multiple requests. Once the value is read, it -is cleared (unless reset). Although C 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 part of the -tutorial to take advantage of C. +As discussed in the previous chapter of the tutorial, C allows +you to set variables in a way that is very similar to C, but it +will remain set across multiple requests. Once the value is read, it +is cleared (unless reset). Although C 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 chapter of the tutorial to +take advantage of C. First, open C and modify C to match the following (everything after the model search line of code diff --git a/lib/Catalyst/Manual/Tutorial/Authorization.pod b/lib/Catalyst/Manual/Tutorial/Authorization.pod index 2c3451f..66c6612 100644 --- a/lib/Catalyst/Manual/Tutorial/Authorization.pod +++ b/lib/Catalyst/Manual/Tutorial/Authorization.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,8 +56,8 @@ L =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 @@ -248,7 +248,7 @@ way to demonstrate that TT templates will not be used if the response 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 to an action that shows an "unauthorized" page). +Chapter 3 or C to an action that shows an "unauthorized" page). B: If you want to keep your existing C method, you can create a new copy and comment out the original by making it look like a diff --git a/lib/Catalyst/Manual/Tutorial/BasicCRUD.pod b/lib/Catalyst/Manual/Tutorial/BasicCRUD.pod index 1ae6394..0f7e68c 100644 --- a/lib/Catalyst/Manual/Tutorial/BasicCRUD.pod +++ b/lib/Catalyst/Manual/Tutorial/BasicCRUD.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,22 +56,22 @@ L =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 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, -L, 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 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, +L, and L. You can checkout the source code for this example from the catalyst @@ -185,7 +185,7 @@ The TT C directive allows access to a variety of plugin modules to the base TT capabilities. Here, the plugin allows L "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 Feature @@ -233,7 +233,7 @@ Ctrl+Reload your browser at the C page). =head1 CONVERT TO A CHAINED ACTION Although the example above uses the same C 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 in C you @@ -327,7 +327,7 @@ chain. 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, @@ -573,7 +573,7 @@ C template seen in earlier examples. Finally, click B 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 @@ -860,11 +860,11 @@ be displayed. =head2 Using C to Pass Query Parameters -There are several ways to pass information across a redirect. One -option is to use the C 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 and update the existing C +There are several ways to pass information across a redirect. One +option is to use the C 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 and update the existing C method to match the following: =head2 delete @@ -916,7 +916,7 @@ should return. B Another popular method for maintaining server-side information across a redirect is to use the C technique we -discuss in the next part of the tutorial, +discuss in the next chapter of the tutorial, L. While C is a "slicker" mechanism in that it's all handled by the server and doesn't "pollute" your URLs, B feature, DBIC automatically looks for your Result Class files in a subdirectory of the Schema directory called C (the files in C were already there -from Part 3 of the tutorial; the files in C +from Chapter 3 of the tutorial; the files in C 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 diff --git a/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod b/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod index 7cd1554..978fb91 100644 --- a/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod +++ b/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,8 +56,9 @@ L =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 @@ -121,9 +122,8 @@ Also note that as of Catalyst 5.7000, you will not have the helper scripts unless you install both L and L. -In this first part of the tutorial, use the Catalyst -C script to initialize the framework for an -application called C: +In this first chapter of the tutorial, use the Catalyst C +script to initialize the framework for an application called C: $ catalyst.pl Hello created "Hello" @@ -359,7 +359,7 @@ Template Toolkit is a very full featured template facility, with excellent documentation at L, 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 template file (put it in the C under the C directory that is the base of your application). Here is diff --git a/lib/Catalyst/Manual/Tutorial/Debugging.pod b/lib/Catalyst/Manual/Tutorial/Debugging.pod index 85e80fd..a7e175a 100644 --- a/lib/Catalyst/Manual/Tutorial/Debugging.pod +++ b/lib/Catalyst/Manual/Tutorial/Debugging.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,7 +56,7 @@ L =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 diff --git a/lib/Catalyst/Manual/Tutorial/Intro.pod b/lib/Catalyst/Manual/Tutorial/Intro.pod index 78bf5eb..b35ad7b 100644 --- a/lib/Catalyst/Manual/Tutorial/Intro.pod +++ b/lib/Catalyst/Manual/Tutorial/Intro.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -72,7 +72,7 @@ catalyst subversion repository by issuing the command: 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 You can run the test cases for the final code through Part 8 +B 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 section in -your tests, substitute C for -C in the URL above. However, you will also need to +your tests, substitute C for +C in the URL above. However, you will also need to run the following additional commands: sudo aptitude -y install libhtml-formfu-perl libmoose-perl \ @@ -625,7 +625,7 @@ pulling up C in your web browser (as mentioned earlier, change C 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". diff --git a/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod b/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod index 2b94d3a..118da33 100644 --- a/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod +++ b/lib/Catalyst/Manual/Tutorial/MoreCatalystBasics.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,13 +56,13 @@ L =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 @@ -74,7 +74,7 @@ L. The remainder of the tutorial will build an application called C. First use the Catalyst C script to initialize the framework for the C application (make sure you aren't still inside the -directory of the C application from the previous part of the +directory of the C application from the previous chapter of the tutorial or in a directory that already has a "MyApp" subdirectory): $ catalyst.pl MyApp @@ -86,7 +86,7 @@ tutorial or in a directory that already has a "MyApp" subdirectory): 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 and C substituted for C and C. @@ -138,7 +138,7 @@ L file (versus having the values 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 If you are using a version of L prior to version 1.06, be aware @@ -247,7 +247,7 @@ actions: created "/home/me/MyApp/script/../lib/MyApp/Controller/Books.pm" created "/home/me/MyApp/script/../t/controller_Books.t" -Then edit C (as discussed in Part 2 of +Then edit C (as discussed in Chapter 2 of the Tutorial, Catalyst has a separate directory under C for each of the three parts of MVC: C, C, and C) and add the following method to the controller: @@ -374,7 +374,7 @@ types not discussed here (C and C). =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 selects the I of view to use, with the actual @@ -407,7 +407,7 @@ L Both helpers are similar. C creates the C file and leaves the creation of any hierarchical template organization entirely up to you. (It also creates a C file for testing; -test cases will be discussed in Part 8.) C, on the other hand, +test cases will be discussed in Chapter 8.) C, 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. @@ -970,7 +970,7 @@ B The Catalyst stash only lasts for a single HTTP request. If you need to retain information across requests you can use L (we will use -Catalyst sessions in the Authentication part of the tutorial). +Catalyst sessions in the Authentication chapter of the tutorial). =item * @@ -1117,7 +1117,7 @@ Debian 5 uses the older DBIC C vs. the newer C technique. For new applications, please try to use C since it more easily supports a very useful DBIC technique called "ResultSet Classes." We will migrate to -C in Part 4 (BasicCRUD) of this tutorial. +C in Chapter 4 (BasicCRUD) of this tutorial. =head2 Updating the Generated DBIC Schema Files @@ -1330,8 +1330,8 @@ and asked your browser to view the page source. =head1 OPTIONAL INFORMATION -B, +B, if you wish.> @@ -1426,8 +1426,8 @@ as before. B Please note that if you use the default template technique, you will B be able to use either the C<$c-Eforward> or -the C<$c-Edetach> mechanisms (these are discussed in Part 2 and -Part 9 of the Tutorial). +the C<$c-Edetach> mechanisms (these are discussed in Chapter 2 and +Chapter 9 of the Tutorial). =head2 Return To A Manually-Specified Template diff --git a/lib/Catalyst/Manual/Tutorial/Testing.pod b/lib/Catalyst/Manual/Tutorial/Testing.pod index 25acec4..03061f8 100644 --- a/lib/Catalyst/Manual/Tutorial/Testing.pod +++ b/lib/Catalyst/Manual/Tutorial/Testing.pod @@ -1,11 +1,11 @@ =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 for the Catalyst tutorial. +This is B for the Catalyst tutorial. L @@ -56,12 +56,12 @@ L =head1 DESCRIPTION -You may have noticed that the Catalyst Helper scripts automatically -create basic C<.t> test scripts under the C 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 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 @@ -289,10 +289,10 @@ or $ DBIC_TRACE=0 CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t -Experiment with the C, C -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, C 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: