For information about current developments and future releases, see:
http://maypole.perl.org/?TheRoadmap
-2.06 XXX
+2.06 Wed Dec 29 01:30:00 2004
Fixes:
+ - Minor restructuring of the manual so search.cpan.org indexes it better
- #9129: Skip t/apache_mvc.t if Apache::Request isn't installed
+
2.05 Fri Dec 24 03:20:00 2004
- Revised and updated documentation. Many thanks to Dave Howorth for his
-=head1 The Maypole Manual
+=head1 NAME
+
+Maypole::Manual - The Maypole Manual
+
+=head1 DESCRIPTION
The Maypole documentation is arranged over several files; this is
the right one to start with, as it provides an overview of the
-=head1 Introduction to Maypole
+=head1 NAME
+
+Maypole::Manual::About - Introduction to Maypole
+
+=head1 DESCRIPTION
This chapter serves as a gentle introduction to Maypole and setting up
Maypole applications. We look at what Maypole is, how to get it up and
-=head1 The Beer Database, Twice
+=head1 NAME
+
+Maypole::Manual::Beer - The Beer Database, Twice
+
+=head1 DESCRIPTION
We briefly introduced the "beer database" example in the
L<Introduction to Maypole|Maypole::Manual::About> chapter, where we
-=head1 The Maypole iBuySpy Portal
+=head1 NAME
+
+Maypole::Manual::BugSpy - The Maypole iBuySpy Portal
+
+=head1 DESCRIPTION
I think it's good fun to compare Maypole against other frameworks,
so here's how to build the ASP.NET tutorial site in Maypole.
-=head1 Flox: A Free Social Networking Site
+=head1 NAME
+
+Maypole::Manual::Flox - Flox: A Free Social Networking Site
+
+=head1 DESCRIPTION
Friendster, Tribe, and now Google's Orkut - it seems like in early 2004,
everyone wanted to be a social networking site. At the time, I was too
-=head1 Maypole Model Classes
+=head1 NAME
+
+Maypole::Manual::Model - Maypole Model Classes
+
+=head1 DESCRIPTION
Maypole's model classes provide an interface to your data store.
In principle Maypole can connect to pretty much any data source,
-=head1 Maypole Request Hacking Cookbook
+=head1 NAME
+
+Maypole::Manual::Request - Maypole Request Hacking Cookbook
+
+=head1 DESCRIPTION
Hacks; design patterns; recipes: call it what you like, this chapter is a
developing collection of techniques which can be slotted in to Maypole
-=head1 Maypole's Standard Templates and Actions
+=head1 NAME
+
+Maypole::Manual::StandardTemplates - Maypole's Standard Templates and Actions
+
+=head1 DESCRIPTION
As we saw in our Create-Read-Update-Delete (CRUD) example,
Maypole does all it can to make your life
-=head1 Maypole View Classes
+=head1 NAME
+
+Maypole::Manual::View - Maypole View Classes
+
+=head1 DESCRIPTION
In a large application, you will almost certainly want to customize the
layout and design of the output pages. This task may even be the purview
=pod
-=head1 Maypole's Request Workflow
+=head1 NAME
+
+Maypole::Manual::Workflow - Maypole's Request Workflow
+
+=head1 DESCRIPTION
This chapter describes the progress of a request through Maypole.
Previous
L<Standard Templates and Actions|Maypole::Manual::StandardTemplates>
-
+=cut
=head2 paths
-Returns search paths for templates. the default method returns factory, custom
-and E<lt>tablenameE<gt> under the configured template root.
+Returns search paths for templates. the default method returns folders for the
+model class's C<moniker>, factory, custom under the configured template root.
=head2 vars
my $mock_cgi = new Test::MockModule('CGI::Simple');
$mock_cgi->mock(path_info => sub {
delete $_[0]->{'.path_info'};
- goto $mock_cgi->original('path_info')
+ my $orig_path_info = $mock_cgi->original('path_info');
+ goto $orig_path_info;
});
# run()