added new attribute to Maypole::Config - request_options

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

diff --git a/lib/Maypole/Config.pm b/lib/Maypole/Config.pm
index cc9a9f59250b9a9faa74f4689b3629e7991c3b65..247398675015cdec1ac1aa1f66acec45f4f711f9 100644 (file)
--- a/lib/Maypole/Config.pm
+++ b/lib/Maypole/Config.pm
@@ -9,8 +9,9 @@ our $VERSION = "1." . sprintf "%04d", q$Rev$ =~ /: (\d+)/;
 
 # Public accessors.
 __PACKAGE__->mk_accessors(
-     qw( view view_options uri_base template_root model loader display_tables
-         ok_tables rows_per_page dsn user pass opts application_name)
+     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 additional build_form_elements request_options)
 );
 
 # Should only be modified by model.
@@ -46,6 +47,10 @@ Optional.
 
 Contains a list of all tables, if supported by model.
 
+=head3 template_extension
+
+Optional template file extension.
+
 =head3 template_root
 
 This is where your application can find its templates.
@@ -60,6 +65,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
@@ -110,8 +124,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: