Merge commit '2.13' into HEAD

[maypole.git] / lib / Maypole / Config.pm

diff --git a/lib/Maypole/Config.pm b/lib/Maypole/Config.pm
index 040a4c8e8baa0975d9a3bffcebca788a57655e01..3e8081177b2a276965072fdad92b96c2f43cf20e 100644 (file)
--- a/lib/Maypole/Config.pm
+++ b/lib/Maypole/Config.pm
@@ -5,14 +5,19 @@ use attributes ();
 use strict;
 use warnings;
 
-our $VERSION = "1." . sprintf "%04d", q$Rev: 334 $ =~ /: (\d+)/;
+our $VERSION = 2.121;
 
 # Public accessors.
 __PACKAGE__->mk_accessors(
-     qw( view view_options uri_base template_root template_extension model
-         loader display_tables ok_tables rows_per_page dsn user pass opts
-         application_name)
-);
+                         qw(
+                             view view_options template_root template_extension build_form_elements
+                             uri_base rows_per_page application_name
+                             model loader display_tables ok_tables
+                             dsn user pass opts
+                             additional
+                             request_options
+                            )
+                         );
 
 # Should only be modified by model.
 __PACKAGE__->mk_ro_accessors(qw( classes tables));
@@ -65,6 +70,15 @@ makes URLs.
 The name of the view class for your Maypole Application. Defaults to
 "Maypole::View::TT".
 
+=head3 build_form_elements
+
+Globally specify whether to build form elements; populating the cgi metadata with 
+autogenerated HTML::Element widgets for the class/object.
+
+Can be over-ridden per action using the method of the same name for the request.
+
+If not set, then Maypole will assume it is true.
+
 =head3 view_options
 
 A hash of configuration options for the view class. Consult the documentation
@@ -115,8 +129,21 @@ Other options to the DBI connect call.
 
 Username to log into the database with.
 
+=head3 build_form_elements
+
+Flag specifying whether to build metadata for form elements in factory templates
+
+=head3 request_options
+
+Hashref of options passed when creating cgi or apache request
+
 =head2 Adding additional configuration data
 
+You can use the 'additional' attribute for stashing additional info, especially from additional_data method,
+i.e. $r->config->additional({foo=>bar});
+
+Or..
+
 If your modules need to store additional configuration data for their 
 own use or to make available to templates, add a line like this to your 
 module: