DFV model tested and working, new additional method in Maypole::Config, new warn...

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

diff --git a/lib/Maypole/Config.pm b/lib/Maypole/Config.pm
index 6a236c829c8ecf950651cb2ed725472757264125..2cf65daba17eca9111aa0e7ff1cdd0e515ab11bf 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 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)
 );
 
 # Should only be modified by model.
@@ -34,22 +35,29 @@ This class stores all configuration data for your Maypole application.
 
 This should be a string containing your application's name.
 
+Optional. Is used in the factory templates.
+
 =head3 rows_per_page
 
 This is the number of rows your application should display per page.
 
+Optional.
+
 =head3 tables
 
 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.
 
 =head3 uri_base
 
-This is the URI base that should be prepended to your application when
-Maypole
+This is the URI base that should be prepended to your application when Maypole
 makes URLs.
 
 =head3 view
@@ -57,6 +65,11 @@ makes URLs.
 The name of the view class for your Maypole Application. Defaults to
 "Maypole::View::TT".
 
+=head3 view_options
+
+A hash of configuration options for the view class. Consult the documentation
+for your chosen view class for information on available configuration options.
+
 =head2 Model-Related
 
 =head3 classes
@@ -104,6 +117,11 @@ Username to log into the database with.
 
 =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: