use strict;
use warnings;
-our $VERSION = "1." . sprintf "%04d", q$Rev$ =~ /: (\d+)/;
+our $VERSION = "1." . sprintf "%04d", q$Rev: 570 $ =~ /: (\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 build_form_elements request_options)
);
# Should only be modified by model.
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
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
+for your chosen view class for information on available configuration options.
+
=head2 Model-Related
=head3 classes
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: