[Catalyst-commits] r6510 - / trunk/Catalyst-Manual/lib/Catalyst/Manual

[zarquon at dev.catalyst.perl.org]

Author: zarquon
Date: 2007-07-07 00:43:08 +0100 (Sat, 07 Jul 2007)
New Revision: 6510

Modified:
   /
   trunk/Catalyst-Manual/lib/Catalyst/Manual/Cookbook.pod
Log:
 r10645 at zaphod:  kd | 2007-07-07 09:01:08 +1000
 abraxxa's uri_for parent path explanation and some word wrap formatting



Property changes on: 
___________________________________________________________________
Name: svk:merge
   - 1b129c88-ebf4-0310-add9-f09427935aba:/local/catalyst:4278
1c72fc7c-9ce4-42af-bf25-3bfe470ff1e8:/local/Catalyst:10550
3b9770f9-e80c-0410-a7de-cd203d167417:/local/catalyst:3514
dd8ad9ea-0304-0410-a433-df5f223e7bc0:/local/Catalyst:6909
   + 1b129c88-ebf4-0310-add9-f09427935aba:/local/catalyst:4278
1c72fc7c-9ce4-42af-bf25-3bfe470ff1e8:/local/Catalyst:10645
3b9770f9-e80c-0410-a7de-cd203d167417:/local/catalyst:3514
dd8ad9ea-0304-0410-a433-df5f223e7bc0:/local/Catalyst:6909

Modified: trunk/Catalyst-Manual/lib/Catalyst/Manual/Cookbook.pod
===================================================================
--- trunk/Catalyst-Manual/lib/Catalyst/Manual/Cookbook.pod	2007-07-06 02:16:21 UTC (rev 6509)
+++ trunk/Catalyst-Manual/lib/Catalyst/Manual/Cookbook.pod	2007-07-06 23:43:08 UTC (rev 6510)
@@ -10,21 +10,23 @@
 
 =head1 Basics
 
-These recipes cover some basic stuff that is worth knowing for catalyst developers.
+These recipes cover some basic stuff that is worth knowing for
+catalyst developers.
 
 =head2 Delivering a Custom Error Page
 
 By default, Catalyst will display its own error page whenever it
 encounters an error in your application. When running under C<-Debug>
-mode, the error page is a useful screen including the error message and
-L<Data::Dump> output of the relevant parts of the C<$c> context object. 
-When not in C<-Debug>, users see a simple "Please come back later" screen.
+mode, the error page is a useful screen including the error message
+and L<Data::Dump> output of the relevant parts of the C<$c> context
+object.  When not in C<-Debug>, users see a simple "Please come back
+later" screen.
 
-To use a custom error page, use a special C<end> method to short-circuit
-the error processing. The following is an example; you might want to
-adjust it further depending on the needs of your application (for
-example, any calls to C<fillform> will probably need to go into this
-C<end> method; see L<Catalyst::Plugin::FillInForm>).
+To use a custom error page, use a special C<end> method to
+short-circuit the error processing. The following is an example; you
+might want to adjust it further depending on the needs of your
+application (for example, any calls to C<fillform> will probably need
+to go into this C<end> method; see L<Catalyst::Plugin::FillInForm>).
 
     sub end : Private {
         my ( $self, $c ) = @_;
@@ -52,8 +54,8 @@
 
 =head2 Disable statistics
 
-Just add this line to your application class if you don't want those nifty
-statistics in your debug messages.
+Just add this line to your application class if you don't want those
+nifty statistics in your debug messages.
 
     sub Catalyst::Log::info { }
 
@@ -67,32 +69,34 @@
 
 =head2 Sessions
 
-When you have your users identified, you will want to somehow remember that
-fact, to save them from having to identify themselves for every single
-page. One way to do this is to send the username and password parameters in
-every single page, but that's ugly, and won't work for static pages. 
+When you have your users identified, you will want to somehow remember
+that fact, to save them from having to identify themselves for every
+single page. One way to do this is to send the username and password
+parameters in every single page, but that's ugly, and won't work for
+static pages.
 
-Sessions are a method of saving data related to some transaction, and giving
-the whole collection a single ID. This ID is then given to the user to return
-to us on every page they visit while logged in. The usual way to do this is
-using a browser cookie.
+Sessions are a method of saving data related to some transaction, and
+giving the whole collection a single ID. This ID is then given to the
+user to return to us on every page they visit while logged in. The
+usual way to do this is using a browser cookie.
 
 Catalyst uses two types of plugins to represent sessions:
 
 =head3 State
 
-A State module is used to keep track of the state of the session between the
-users browser, and your application.  
+A State module is used to keep track of the state of the session
+between the users browser, and your application.
 
-A common example is the Cookie state module, which sends the browser a cookie
-containing the session ID. It will use default value for the cookie name and
-domain, so will "just work" when used. 
+A common example is the Cookie state module, which sends the browser a
+cookie containing the session ID. It will use default value for the
+cookie name and domain, so will "just work" when used.
 
 =head3 Store
 
-A Store module is used to hold all the data relating to your session, for
-example the users ID, or the items for their shopping cart. You can store data
-in memory (FastMmap), in a file (File) or in a database (DBI).
+A Store module is used to hold all the data relating to your session,
+for example the users ID, or the items for their shopping cart. You
+can store data in memory (FastMmap), in a file (File) or in a database
+(DBI).
 
 =head3 Authentication magic
 
@@ -103,7 +107,8 @@
 =head3 Using a session
 
 Once the session modules are loaded, the session is available as C<<
-$c->session >>, and can be writen to and read from as a simple hash reference.
+$c->session >>, and can be writen to and read from as a simple hash
+reference.
 
 =head3 EXAMPLE
 
@@ -158,8 +163,8 @@
 =head3 Using YAML
 
 YAML 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.
+files. It's a great way to keep your Catalyst application
+configuration in one easy-to-understand location.
 
 In your application class (e.g. C<lib/MyApp.pm>):
 
@@ -310,8 +315,8 @@
      # do something restricted here
   }
 
-You can also use the C<assert_user_roles> method. This just gives an error if
-the current user does not have one of the required roles:
+You can also use the C<assert_user_roles> method. This just gives an
+error if the current user does not have one of the required roles:
 
   sub also_restricted : Global {
     my ( $self, $c ) = @_;
@@ -327,27 +332,29 @@
 =item Verification
 
 Getting the user to identify themselves, by giving you some piece of
-information known only to you and the user. Then you can assume that the user
-is who they say they are. This is called B<credential verification>.
+information known only to you and the user. Then you can assume that
+the user is who they say they are. This is called B<credential
+verification>.
 
 =item Authorization
 
-Making sure the user only accesses functions you want them to access. This is
-done by checking the verified users data against your internal list of groups,
-or allowed persons for the current page.
+Making sure the user only accesses functions you want them to
+access. This is done by checking the verified users data against your
+internal list of groups, or allowed persons for the current page.
 
 =back
 
 =head3 Modules
 
-The Catalyst Authentication system is made up of many interacting modules, to
-give you the most flexibility possible.
+The Catalyst Authentication system is made up of many interacting
+modules, to give you the most flexibility possible.
 
 =head4 Credential verifiers
 
-A Credential module tables the user input, and passes it to a Store, or some
-other system, for verification. Typically, a user object is created by either
-this module or the Store and made accessible by a C<< $c->user >> call.
+A Credential module tables the user input, and passes it to a Store,
+or some other system, for verification. Typically, a user object is
+created by either this module or the Store and made accessible by a
+C<< $c->user >> call.
 
 Examples:
 
@@ -357,9 +364,9 @@
 
 =head3 Storage backends
 
-A Storage backend contains the actual data representing the users. It is
-queried by the credential verifiers. Updating the store is not done within
-this system, you will need to do it yourself.
+A Storage backend contains the actual data representing the users. It
+is queried by the credential verifiers. Updating the store is not done
+within this system, you will need to do it yourself.
 
 Examples:
 
@@ -368,8 +375,8 @@
 
 =head3 User objects
 
-A User object is created by either the storage backend or the credential
-verifier, and filled with the retrieved user information.
+A User object is created by either the storage backend or the
+credential verifier, and filled with the retrieved user information.
 
 Examples:
 
@@ -377,27 +384,28 @@
 
 =head3 ACL authorization
 
-ACL stands for Access Control List. The ACL plugin allows you to regulate
-access on a path by path basis, by listing which users, or roles, have access
-to which paths.
+ACL stands for Access Control List. The ACL plugin allows you to
+regulate access on a path by path basis, by listing which users, or
+roles, have access to which paths.
 
 =head3 Roles authorization
 
-Authorization by roles is for assigning users to groups, which can then be
-assigned to ACLs, or just checked when needed.
+Authorization by roles is for assigning users to groups, which can
+then be assigned to ACLs, or just checked when needed.
 
 =head3 Logging in
 
 When you have chosen your modules, all you need to do is call the C<<
 $c->login >> method. If called with no parameters, it will try to find
-suitable parameters, such as B<username> and B<password>, or you can pass it
-these values.
+suitable parameters, such as B<username> and B<password>, or you can
+pass it these values.
 
 =head3 Checking roles
 
-Role checking is done by using the C<< $c->check_user_roles >> method, this will
-check using the currently logged in user (via C<< $c->user >>). You pass it
-the name of a role to check, and it returns true if the user is a member.
+Role checking is done by using the C<< $c->check_user_roles >> method,
+this will check using the currently logged in user (via C<< $c->user
+>>). You pass it the name of a role to check, and it returns true if
+the user is a member.
 
 =head3 EXAMPLE
 
@@ -436,17 +444,17 @@
 
 =head3 Using authentication in a testing environment
 
-Ideally, to write tests for authentication/authorization code one would first
-set up a test database with known data, then use
-L<Test::WWW::Mechanize::Catalyst> to simulate a user logging in. Unfortunately
-the former can be rather awkward, which is why it's a good thing that the
-authentication framework is so flexible.
+Ideally, to write tests for authentication/authorization code one
+would first set up a test database with known data, then use
+L<Test::WWW::Mechanize::Catalyst> to simulate a user logging
+in. Unfortunately the former can be rather awkward, which is why it's
+a good thing that the authentication framework is so flexible.
 
-Instead of using a test database, one can simply change the authentication
-store to something a bit easier to deal with in a testing
-environment. Additionally, this has the advantage of not modifying one's
-database, which can be problematic if one forgets to use the testing instead of
-production database.
+Instead of using a test database, one can simply change the
+authentication store to something a bit easier to deal with in a
+testing environment. Additionally, this has the advantage of not
+modifying one's database, which can be problematic if one forgets to
+use the testing instead of production database.
 
 e.g.,
 
@@ -470,16 +478,17 @@
 
 =head3 Introduction
 
-Authorization is the step that comes after authentication. Authentication
-establishes that the user agent is really representing the user we think it's
-representing, and then authorization determines what this user is allowed to
-do.
+Authorization is the step that comes after
+authentication. Authentication establishes that the user agent is
+really representing the user we think it's representing, and then
+authorization determines what this user is allowed to do.
 
 =head3 Role Based Access Control
 
-Under role based access control each user is allowed to perform any number of
-roles. For example, at a zoo no one but specially trained personnel can enter
-the moose cage (Mynd you, møøse bites kan be pretty nasti!). For example: 
+Under role based access control each user is allowed to perform any
+number of roles. For example, at a zoo no one but specially trained
+personnel can enter the moose cage (Mynd you, møøse bites kan be
+pretty nasti!). For example:
 
     package Zoo::Controller::MooseCage;
 
@@ -489,12 +498,12 @@
         $c->model( "Moose" )->eat( $c->req->param("food") );
     }
 
-With this action, anyone can just come into the moose cage and feed the moose,
-which is a very dangerous thing. We need to restrict this action, so that only
-a qualified moose feeder can perform that action.
+With this action, anyone can just come into the moose cage and feed
+the moose, which is a very dangerous thing. We need to restrict this
+action, so that only a qualified moose feeder can perform that action.
 
-The Authorization::Roles plugin let's us perform role based access control
-checks. Let's load it:
+The Authorization::Roles plugin let's us perform role based access
+control checks. Let's load it:
 
     use Catalyst qw/
         Authentication # yadda yadda
@@ -513,11 +522,11 @@
         }
     }
 
-This checks C<< $c->user >>, and only if the user has B<all> the roles in the
-list, a true value is returned.
+This checks C<< $c->user >>, and only if the user has B<all> the roles
+in the list, a true value is returned.
 
-C<check_roles> has a sister method, C<assert_roles>, which throws an exception
-if any roles are missing.
+C<check_roles> has a sister method, C<assert_roles>, which throws an
+exception if any roles are missing.
 
 Some roles that might actually make sense in, say, a forum application:
 
@@ -533,62 +542,65 @@
 
 =back
 
-each with a distinct task (system administration versus content administration).
+each with a distinct task (system administration versus content
+administration).
 
 =head3 Access Control Lists
 
 Checking for roles all the time can be tedious and error prone.
 
-The Authorization::ACL plugin let's us declare where we'd like checks to be
-done automatically for us.
+The Authorization::ACL plugin let's us declare where we'd like checks
+to be done automatically for us.
 
 For example, we may want to completely block out anyone who isn't a
 C<moose_feeder> from the entire C<MooseCage> controller:
 
     Zoo->deny_access_unless( "/moose_cage", [qw/moose_feeder/] );
 
-The role list behaves in the same way as C<check_roles>. However, the ACL
-plugin isn't limited to just interacting with the Roles plugin. We can use a
-code reference instead. For example, to allow either moose trainers or moose
-feeders into the moose cage, we can create a more complex check:
+The role list behaves in the same way as C<check_roles>. However, the
+ACL plugin isn't limited to just interacting with the Roles plugin. We
+can use a code reference instead. For example, to allow either moose
+trainers or moose feeders into the moose cage, we can create a more
+complex check:
 
     Zoo->deny_access_unless( "/moose_cage", sub {
         my $c = shift;
         $c->check_roles( "moose_trainer" ) || $c->check_roles( "moose_feeder" );
     });
 
-The more specific a role, the earlier it will be checked. Let's say moose
-feeders are now restricted to only the C<feed_moose> action, while moose
-trainers get access everywhere:
+The more specific a role, the earlier it will be checked. Let's say
+moose feeders are now restricted to only the C<feed_moose> action,
+while moose trainers get access everywhere:
 
     Zoo->deny_access_unless( "/moose_cage", [qw/moose_trainer/] );
     Zoo->allow_access_if( "/moose_cage/feed_moose", [qw/moose_feeder/]);
 
-When the C<feed_moose> action is accessed the second check will be made. If the
-user is a C<moose_feeder>, then access will be immediately granted. Otherwise,
-the next rule in line will be tested - the one checking for a C<moose_trainer>.
-If this rule is not satisfied, access will be immediately denied.
+When the C<feed_moose> action is accessed the second check will be
+made. If the user is a C<moose_feeder>, then access will be
+immediately granted. Otherwise, the next rule in line will be tested -
+the one checking for a C<moose_trainer>.  If this rule is not
+satisfied, access will be immediately denied.
 
-Rules applied to the same path will be checked in the order they were added.
+Rules applied to the same path will be checked in the order they were
+added.
 
-Lastly, handling access denial events is done by creating an C<access_denied>
-private action:
+Lastly, handling access denial events is done by creating an
+C<access_denied> private action:
 
     sub access_denied : Private {
         my ( $self, $c, $action ) = @_;
-
-        
     }
 
-This action works much like auto, in that it is inherited across namespaces
-(not like object oriented code). This means that the C<access_denied> action
-which is B<nearest> to the action which was blocked will be triggered.
+This action works much like auto, in that it is inherited across
+namespaces (not like object oriented code). This means that the
+C<access_denied> action which is B<nearest> to the action which was
+blocked will be triggered.
 
-If this action does not exist, an error will be thrown, which you can clean up
-in your C<end> private action instead.
+If this action does not exist, an error will be thrown, which you can
+clean up in your C<end> private action instead.
 
-Also, it's important to note that if you restrict access to "/" then C<end>,
-C<default>, etc will also be restricted.
+Also, it's important to note that if you restrict access to "/" then
+C<end>, C<default>, etc will also be restricted.
 
    MyApp->acl_allow_root_internals;
 
@@ -603,10 +615,10 @@
 
 =head2 Using existing DBIC (etc.) classes with Catalyst
 
-Many people have existing Model classes that they would like to use with
-Catalyst (or, conversely, they want to write Catalyst models that can be
-used outside of Catalyst, e.g.  in a cron job). It's trivial to write a
-simple component in Catalyst that slurps in an outside Model:
+Many people have existing Model classes that they would like to use
+with Catalyst (or, conversely, they want to write Catalyst models that
+can be used outside of Catalyst, e.g.  in a cron job). It's trivial to
+write a simple component in Catalyst that slurps in an outside Model:
 
     package MyApp::Model::DB;
     use base qw/Catalyst::Model::DBIC::Schema/;
@@ -912,16 +924,36 @@
 
     <a href="[% c.uri_for('/login') %]">Login Here</a>
 
-Although the parameter starts with a forward slash, this is relative to the application root, not the webserver root. This is important to remember. So, if your application is installed at http://www.domain.com/Calendar, then the link would be http://www.mydomain.com/Calendar/Login. If you move your application to a different domain or path, then that link will still be correct.
+Although the parameter starts with a forward slash, this is relative
+to the application root, not the webserver root. This is important to
+remember. So, if your application is installed at
+http://www.domain.com/Calendar, then the link would be
+http://www.mydomain.com/Calendar/Login. If you move your application
+to a different domain or path, then that link will still be correct.
 
 Likewise,
 
     <a href="[% c.uri_for('2005','10', '24') %]">October, 24 2005</a>
 
-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 http://www.domain.com/Calendar/Display/2005/10/24.
+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
+http://www.domain.com/Calendar/Display/2005/10/24.
 
-Once again, this allows you to move your application around without having to worry about broken links. But there's something else, as well. Since the links are generated by uri_for, you can use the same template file by several different controllers, and each controller will get the links that its supposed to. Since we believe in Don't Repeat Yourself, this is particularly helpful if you have common elements in your site that you want to keep in one file.
+If you want to link to a parent uri of your current namespace you can
+prefix the arguments with multiple '../':
 
+    <a href="[% c.uri_for('../../view', stashed_object.id) %]">User view</a>
+
+Once again, this allows you to move your application around without
+having to worry about broken links. But there's something else, as
+well. Since the links are generated by uri_for, you can use the same
+template file by several different controllers, and each controller
+will get the links that its supposed to. Since we believe in Don't
+Repeat Yourself, this is particularly helpful if you have common
+elements in your site that you want to keep in one file.
+
 Further Reading:
 
 L<http://search.cpan.org/perldoc?Catalyst>
@@ -1093,12 +1125,13 @@
 
 =head3 Introduction
 
-A Catalyst application is driven by one or more Controller modules. There are
-a number of ways that Catalyst can decide which of the methods in your
-controller modules it should call. Controller methods are also called actions,
-because they determine how your catalyst application should (re-)act to any
-given URL. When the application is started up, catalyst looks at all your
-actions, and decides which URLs they map to.
+A Catalyst application is driven by one or more Controller
+modules. There are a number of ways that Catalyst can decide which of
+the methods in your controller modules it should call. Controller
+methods are also called actions, because they determine how your
+catalyst application should (re-)act to any given URL. When the
+application is started up, catalyst looks at all your actions, and
+decides which URLs they map to.
 
 =head3 Type attributes
 
@@ -1118,8 +1151,9 @@
 =item Path
 
 A Path attribute also takes an argument, this can be either a relative
-or an absolute path. A relative path will be relative to the controller
-namespace, an absolute path will represent an exact matching URL.
+or an absolute path. A relative path will be relative to the
+controller namespace, an absolute path will represent an exact
+matching URL.
 
  sub my_handles : Path('handles') { .. }
 
@@ -1137,9 +1171,9 @@
 
 =item Local
 
-When using a Local attribute, no parameters are needed, instead, the name of
-the action is matched in the URL. The namespaces created by the name of the
-controller package is always part of the URL.
+When using a Local attribute, no parameters are needed, instead, the
+name of the action is matched in the URL. The namespaces created by
+the name of the controller package is always part of the URL.
 
  sub my_handles : Local { .. }
 
@@ -1149,8 +1183,8 @@
 
 =item Global
 
-A Global attribute is similar to a Local attribute, except that the namespace
-of the controller is ignored, and matching starts at root.
+A Global attribute is similar to a Local attribute, except that the
+namespace of the controller is ignored, and matching starts at root.
 
  sub my_handles : Global { .. }
 
@@ -1160,9 +1194,9 @@
 
 =item Regex
 
-By now you should have figured that a Regex attribute is just what it sounds
-like. This one takes a regular expression, and matches starting from
-root. These differ from the rest as they can match multiple URLs.
+By now you should have figured that a Regex attribute is just what it
+sounds like. This one takes a regular expression, and matches starting
+from root. These differ from the rest as they can match multiple URLs.
 
  sub my_handles : Regex('^handles') { .. }
 
@@ -1195,37 +1229,38 @@
 
 =item Private
 
-Last but not least, there is the Private attribute, which allows you to create
-your own internal actions, which can be forwarded to, but won't be matched as
-URLs.
+Last but not least, there is the Private attribute, which allows you
+to create your own internal actions, which can be forwarded to, but
+won't be matched as URLs.
 
  sub my_handles : Private { .. }
 
 becomes nothing at all..
 
-Catalyst also predefines some special Private actions, which you can override,
-these are:
+Catalyst also predefines some special Private actions, which you can
+override, these are:
 
 =over 4
 
 =item default
 
-The default action will be called, if no other matching action is found. If
-you don't have one of these in your namespace, or any sub part of your
-namespace, you'll get an error page instead. If you want to find out where it
-was the user was trying to go, you can look in the request object using 
-C<< $c->req->path >>.
+The default action will be called, if no other matching action is
+found. If you don't have one of these in your namespace, or any sub
+part of your namespace, you'll get an error page instead. If you want
+to find out where it was the user was trying to go, you can look in
+the request object using C<< $c->req->path >>.
 
  sub default : Private { .. }
 
-works for all unknown URLs, in this controller namespace, or every one if put
-directly into MyApp.pm.
+works for all unknown URLs, in this controller namespace, or every one
+if put directly into MyApp.pm.
 
 =item index 
 
-The index action is called when someone tries to visit the exact namespace of
-your controller. If index, default and matching Path actions are defined, then
-index will be used instead of default and Path.
+The index action is called when someone tries to visit the exact
+namespace of your controller. If index, default and matching Path
+actions are defined, then index will be used instead of default and
+Path.
 
  sub index : Private { .. }
 
@@ -1235,10 +1270,11 @@
 
 =item begin
 
-The begin action is called at the beginning of every request involving this
-namespace directly, before other matching actions are called. It can be used
-to set up variables/data for this particular part of your app. A single begin
-action is called, its always the one most relevant to the current namespace.
+The begin action is called at the beginning of every request involving
+this namespace directly, before other matching actions are called. It
+can be used to set up variables/data for this particular part of your
+app. A single begin action is called, its always the one most relevant
+to the current namespace.
 
  sub begin : Private { .. }
 
@@ -1250,10 +1286,10 @@
 
 =item end
 
-Like begin, this action is always called for the namespace it is in, after
-every other action has finished. It is commonly used to forward processing to
-the View component. A single end action is called, its always the one most
-relevant to the current namespace. 
+Like begin, this action is always called for the namespace it is in,
+after every other action has finished. It is commonly used to forward
+processing to the View component. A single end action is called, its
+always the one most relevant to the current namespace.
 
 
  sub end : Private { .. }
@@ -1266,10 +1302,10 @@
 
 =item auto
 
-Lastly, the auto action is magic in that B<every> auto action in
-the chain of paths up to and including the ending namespace, will be
-called. (In contrast, only one of the begin/end/default actions will be
-called, the relevant one).
+Lastly, the auto action is magic in that B<every> auto action in the
+chain of paths up to and including the ending namespace, will be
+called. (In contrast, only one of the begin/end/default actions will
+be called, the relevant one).
 
  package MyApp.pm;
  sub auto : Private { .. }
@@ -1288,9 +1324,9 @@
 
 =head3 A word of warning
 
-Due to possible namespace conflicts with Plugins, it is advised to only put the
-pre-defined Private actions in your main MyApp.pm file, all others should go
-in a Controller module.
+Due to possible namespace conflicts with Plugins, it is advised to
+only put the pre-defined Private actions in your main MyApp.pm file,
+all others should go in a Controller module.
 
 =head3 More Information