X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2F03_MoreCatalystBasics.pod;h=2c2ea7a757b8e06daf6fc04a51a5e3bdc25fd38e;hp=a13852634d0ed7c9127a70de135d6ffb076cc414;hb=a1de5b6537e37154353b246b66def4f0264b731f;hpb=be0939444127246c8386e4103c79932de3fca9bf diff --git a/lib/Catalyst/Manual/Tutorial/03_MoreCatalystBasics.pod b/lib/Catalyst/Manual/Tutorial/03_MoreCatalystBasics.pod index a138526..2c2ea7a 100644 --- a/lib/Catalyst/Manual/Tutorial/03_MoreCatalystBasics.pod +++ b/lib/Catalyst/Manual/Tutorial/03_MoreCatalystBasics.pod @@ -531,7 +531,7 @@ C. Please stick with the settings above for the duration of the tutorial, but feel free to use whatever options you desire in your applications -(as with most things Perl, there's more than one way to do it...). +(as with most things in Perl, there's more than one way to do it...). B We will use C as the base directory for our template files, with a full naming convention of @@ -855,8 +855,8 @@ when you launch the application). Additionally, the C model can easily be loaded outside of Catalyst, for example, in command-line utilities and/or cron jobs. C provides a very thin "bridge" between -Catalyst this external database model. Once you see how we can add some -powerful features to our DBIC model in +Catalyst and this external database model. Once you see how we can +add some powerful features to our DBIC model in L, the elegance of this approach will start to become more obvious. @@ -881,9 +881,9 @@ L version C<0.05000> or later. =head1 ENABLE THE MODEL IN THE CONTROLLER Open C and un-comment the model code we -left disabled earlier so that your version matches the following (un- -comment the line containing C<[$c-Emodel('DB::Book')-Eall]> and -delete the next 2 lines): +left disabled earlier so that your version matches the following +(un-comment the line containing C<[$c-Emodel('DB::Book')-Eall]> +and delete the next 2 lines): =head2 list @@ -1381,7 +1381,7 @@ alternate way to specify the trace option just in case): $ DBIC_TRACE=1 script/myapp_server.pl -r Make sure that the application loads correctly and that you see the -three dynamically created model class (one for each of the Result +three dynamically created model classes (one for each of the Result Classes we created). Then hit the URL L with your browser @@ -1461,11 +1461,11 @@ html" at the end of every field where a user has control over the information that can appear in that field (and can therefore inject markup or code if you don't "neutralize" those fields). In addition to "| html", Template Toolkit has a variety of other useful filters that -can found in the documentation for L. (While we are -on the topic of security and escaping of dangerous values, one of the -advantages of using tools like DBIC for database access or +can be found in the documentation for L. (While we +are on the topic of security and escaping of dangerous values, one of +the advantages of using tools like DBIC for database access or L for form management [see -L +L] is that they automatically handle most escaping for you and therefore dramatically increase the security of your app.) @@ -1619,12 +1619,12 @@ C<$c-Estash-E{template}> line has changed): You should now be able to access the L URL as before. -B Please note that if you use the default template technique, you +B 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 Chapter 2 and Chapter 9 of the Tutorial). -B Make sure that you do NOT skip the following section +B Make sure that you do B skip the following section before continuing to the next chapter 4 Basic CRUD.