fix links to other Maypole::Manual documents

add a SEE ALSO link to http://maypole.perl.org

git-svn-id: http://svn.maypole.perl.org/Maypole/trunk@285 48953598-375a-da11-a14b-00016c27c3ee

diff --git a/lib/Maypole/Manual.pod b/lib/Maypole/Manual.pod
index b2a97e7f4a26021d0743933343ee682d226417ef..8de39b02b9b4e374be131bb2c07e125e0f32b34b 100644 (file)
--- a/lib/Maypole/Manual.pod
+++ b/lib/Maypole/Manual.pod
@@ -8,7 +8,7 @@ be useful.
 
 =over 4
 
 
 =over 4
 

-=item L<Manual::About> - Overview of the Project
+=item L<Maypole::Manual::About> - Overview of the Project

 
 This document is a general introduction to Maypole: What it is
 (a framework for Web development), what it does (at the basic
 
 This document is a general introduction to Maypole: What it is
 (a framework for Web development), what it does (at the basic


@@ -25,7 +25,7 @@ application--the Beer database--is introduced, set up, and
 discussed. Finally, the path a Maypole request takes as it
 moves through the system is described.
 
 discussed. Finally, the path a Maypole request takes as it
 moves through the system is described.
 

-=item L<Manual::Model> - Model Classes *
+=item L<Maypole::Manual::Model> - Model Classes *

 
 This document introduces the I<model class>, which controls
 the interaction between Maypole and your database. The use of
 
 This document introduces the I<model class>, which controls
 the interaction between Maypole and your database. The use of


@@ -34,19 +34,19 @@ discussed. Maypole's default model class is L<Class::DBI>,
 which basically creates a class for each table in your
 database and provides a variety of convenient methods for
 manipulating each table and its relations. It integrates very
 which basically creates a class for each table in your
 database and provides a variety of convenient methods for
 manipulating each table and its relations. It integrates very

-smoothly with Maypole's default L<view class|"Manual::View">,
+smoothly with Maypole's default L<view class|Maypole::Manual::View>,

 the L<Template> Toolkit.
 
 the L<Template> Toolkit.
 

-=item L<Manual::View> - View Classes *
+=item L<Maypole::Manual::View> - View Classes *

 
 This document is an extensive discussion of Maypole's I<view
 class>, which takes the data produced by the model (see
 
 This document is an extensive discussion of Maypole's I<view
 class>, which takes the data produced by the model (see

-L<above|"Manual::Model">) and sends it through a templating
+L<above|Maypole::Manual::Model>) and sends it through a templating

 system in order to produce output. It focusses chiefly on
 the L<Template> Toolkit, which is Maypole's default templating
 system, but discusses other possibilities.
 
 system in order to produce output. It focusses chiefly on
 the L<Template> Toolkit, which is Maypole's default templating
 system, but discusses other possibilities.
 

-=item L<Manual::StandardTemplates> - Standard actions and templates *
+=item L<Maypole::Manual::StandardTemplates> - Standard actions and templates *

 
 This document discusses the standard actions and templates
 that Maypole uses. The standard actions (method calls that
 
 This document discusses the standard actions and templates
 that Maypole uses. The standard actions (method calls that


@@ -64,26 +64,26 @@ This document also introduces the theory behind Maypole's
 actions and templates, showing you how to write your own
 so that you can have a highly customized application.
 
 actions and templates, showing you how to write your own
 so that you can have a highly customized application.
 

-=item L<Manual::Workflow> - Description of the Maypole Workflow 
+=item L<Maypole::Manual::Workflow> - Description of the Maypole Workflow 

 
 This is a technical document that describes the progress of a
 request through the entire Maypole system. It should be of
 interest chiefly to those people hacking on Maypole itself,
 and not to most of those who are using it.
 
 
 This is a technical document that describes the progress of a
 request through the entire Maypole system. It should be of
 interest chiefly to those people hacking on Maypole itself,
 and not to most of those who are using it.
 

-=item L<Manual::Beer> - The Beer Database Revisited *
+=item L<Maypole::Manual::Beer> - The Beer Database Revisited *

 
 This document gives a close look at the Beer database that
 
 This document gives a close look at the Beer database that

-was introduced in L<Manual::About>.
+was introduced in L<Maypole::Manual::About>.

 
 

-=item L<Manual::Request> - The Request Cookbook 
+=item L<Maypole::Manual::Request> - The Request Cookbook 

 
 This extensive document is Maypole's main "How do I do X?" FAQ.
 It provides a wide variety of cookbook-like techniques that
 are useful both for themselves, and as examples of what sort
 of things can be done with Maypole processes.
 
 
 This extensive document is Maypole's main "How do I do X?" FAQ.
 It provides a wide variety of cookbook-like techniques that
 are useful both for themselves, and as examples of what sort
 of things can be done with Maypole processes.
 

-=item L<Manual::Flox> - Case Study: Flox social network *
+=item L<Maypole::Manual::Flox> - Case Study: Flox social network *

 
 This is an example of how to construct a large Web application
 in Maypole: a "social network", similar to Friendster and
 
 This is an example of how to construct a large Web application
 in Maypole: a "social network", similar to Friendster and


@@ -91,7 +91,7 @@ Orkut. It shows, specifically, the database structure and the
 variety of customized techniques that make such a system
 work.
 
 variety of customized techniques that make such a system
 work.
 

-=item L<Manual::IBuySpy> - Case Study: iBuySpy *
+=item L<Maypole::Manual::IBuySpy> - Case Study: iBuySpy *

 
 This is an example of the C<ASP.NET> sample portal application
 ported to Maypole. L<http://www.ibuyspy.com> is a fictional
 
 This is an example of the C<ASP.NET> sample portal application
 ported to Maypole. L<http://www.ibuyspy.com> is a fictional


@@ -102,6 +102,9 @@ better as a Maypole application.
 
   * indicates incomplete chapters.
 
 
   * indicates incomplete chapters.
 

+=head1 SEE ALSO
+
+L<http://maypole.perl.org>

 
 =head1 AUTHOR
 
 
 =head1 AUTHOR