X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FCookbook.pod;h=58e9d0a29b2969f866c6561f398d57af63fe7e65;hp=6127ceca053c560cc50026da9f5489fb9f6acefe;hb=080bb6202ae1dc9a786bb32afcb391f542c2f0fc;hpb=5336f54651dd781138086b9081b85b6839452a76 diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod index 6127cec..58e9d0a 100644 --- a/lib/Catalyst/Manual/Cookbook.pod +++ b/lib/Catalyst/Manual/Cookbook.pod @@ -70,7 +70,7 @@ Normally you enable the debugging info by adding the C<-Debug> flag to your C statement . However, you can also enable it using environment variable, so you can (for example) get debug info without modifying your application scripts. Just set C or -CMYAPPE_DEBUG> to a true value. +C<< _DEBUG >> to a true value. =head2 Sessions @@ -156,17 +156,17 @@ reference. =head3 More information -L +L -L +L -L +L -L +L -L +L -L +L =head2 Configure your application @@ -180,7 +180,7 @@ L is a method for creating flexible and readable configuration files. It's a great way to keep your Catalyst application configuration in one easy-to-understand location. -Now create C in your application home: +Now create F in your application home: name MyApp @@ -821,17 +821,17 @@ This time, the helper sets several options for us in the generated View. =over -=item +=item * INCLUDE_PATH defines the directories that Template Toolkit should search for the template files. -=item +=item * PRE_PROCESS is used to process configuration options which are common to every template file. -=item +=item * WRAPPER is a file which is processed with each template, usually used to easily provide a common header and footer for every page. @@ -856,7 +856,7 @@ or sections; just put in the content. The WRAPPER will the rest of the page around your template for you. -=head3 $c->stash +=head3 C<< $c->stash >> Of course, having the template system include the header and footer for you isn't all that we want our templates to do. We need to be able to @@ -911,7 +911,7 @@ This is the most basic usage, but Template Toolkit is quite powerful, and allows you to truly keep your presentation logic separate from the rest of your application. -=head3 $c->uri_for() +=head3 C<< $c->uri_for() >> One of my favorite things about Catalyst is the ability to move an application around without having to worry that everything is going to @@ -922,7 +922,7 @@ to "/Calendar", "/Calendar/2005", "/Calendar/2005/10", etc. If you move the application to be at http://www.mydomain.com/Tools/Calendar, then all of those links will suddenly break. -That's where $c->uri_for() comes in. This function will merge its +That's where C<< $c->uri_for() >> comes in. This function will merge its parameters with either the base location for the app, or its current namespace. Let's take a look at a couple of examples. @@ -944,7 +944,7 @@ Likewise, The first parameter does NOT have a forward slash, and so it will be relative to the current namespace. If the application is installed at http://www.domain.com/Calendar. and if the template is called from -MyApp::Controller::Display, then the link would become +C, then the link would become http://www.domain.com/Calendar/Display/2005/10/24. If you want to link to a parent uri of your current namespace you can @@ -962,11 +962,11 @@ elements in your site that you want to keep in one file. Further Reading: -L +L -L +L -L +L