[Catalyst-commits] r12098 - trunk/examples/CatalystAdvent/root/2009/pen

[zamolxes at dev.catalyst.perl.org]

Author: zamolxes
Date: 2009-12-01 02:03:59 +0000 (Tue, 01 Dec 2009)
New Revision: 12098

Modified:
   trunk/examples/CatalystAdvent/root/2009/pen/1.pod
Log:
links on modules


Modified: trunk/examples/CatalystAdvent/root/2009/pen/1.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/pen/1.pod	2009-12-01 02:03:16 UTC (rev 12097)
+++ trunk/examples/CatalystAdvent/root/2009/pen/1.pod	2009-12-01 02:03:59 UTC (rev 12098)
@@ -24,50 +24,50 @@
 
 =head2 What modules are worth a (re-)look?
 
-Catalyst::Model::DBIC::Schema has been rewritten using a traits system to
+L<Catalyst::Model::DBIC::Schema> has been rewritten using a traits system to
 enable plugins to be written and loaded for it easily, and is once again
 a shining example of best practices for model adaptor authoring (many thanks
 to Rafael Kitover aka Caelum for doing the heavy lifting - and for putting up
 with my nitpicking during the process).
 
-CatalystX::RoleApplicator allows us to elegantly add roles to the
+L<CatalystX::RoleApplicator> allows us to elegantly add roles to the
 application, request, response, engine, dispatcher and stats classes in use,
 eliminating the need to construct near-empty classes in order to compose
 together additional functionality. Better still, RoleApplicator is implemented
-using MooseX::RelatedClassRoles so you can use the same interface when you
+using L<MooseX::RelatedClassRoles> so you can use the same interface when you
 hit similar problems in your own code (many thanks to Hans Dieter Pearcey aka
 confound for writing both).
 
-Catalyst::Controller::ActionRole provides the :Does attribute which applies
+L<Catalyst::Controller::ActionRole> provides the :Does attribute which applies
 roles to your action class rather than setting it ala :ActionClass - far
 cleaner and as with RoleApplicator allows multiple behaviours to be used
 at once (merci to both confound, and to Florian Ragwitz aka rafl for this
 one).
 
-Given that, we can now implement things such as Catalyst::ActionRole::ACL -
- which provides declarative role-based authorisation for actions (kudos to
+Given that, we can now implement things such as L<Catalyst::ActionRole::ACL> -
+which provides declarative role-based authorisation for actions (kudos to
 David Wollmann aka converter for this one) - and this can be combined onto
 the same action with other similar modules - for example
-Catalyst::ActionRole::NeedsLogin from CatalystX::SimpleLogin, such that
+L<Catalyst::ActionRole::NeedsLogin> from L<CatalystX::SimpleLogin>, such that
 an un-logged-in user is redirected to the login page and a logged-in user
 is restricted unless they have correct permissions - all on a single controller
 method.
 
-CatalystX::SimpleLogin also illustrates that we're now able to supply
+L<CatalystX::SimpleLogin> also illustrates that we're now able to supply
 actions from controller roles (and method modifiers to existing actions)
-- for example CatalystX::SimpleLogin::TraitFor::Controller::Login::Logout
+- for example L<CatalystX::SimpleLogin::TraitFor::Controller::Login::Logout>
 adds a logout action to your controller (SimpleLogin was created by a
 number of evil geniuses - see the docs for the full list). This is possible
-because of work done on MooseX::MethodAttributes by rafl and Tomas Doran
+because of work done on L<MooseX::MethodAttributes> by rafl and Tomas Doran
 aka t0m, with assorted help, kibitzing and occasional laughter from the Moose
 community.
 
-I should probably also mention Gerda Shank aka gshank's HTML::FormHandler,
+I should probably also mention Gerda Shank aka gshank's L<HTML::FormHandler>,
 which seems to be rapidly gaining in popularity - it's aiming at a different
-problem definition to HTML::FormFu but given its wide adoption perhaps it's
+problem definition to L<HTML::FormFu> but given its wide adoption perhaps it's
 aiming for a better problem definition; I am grumpy and cynical about form
 handling so choose not to express an opinion. But HTML::FormHandler is
-a great example of the same, growing, trend as MooseX::RelatedClassRoles
+a great example of the same, growing, trend as L<MooseX::RelatedClassRoles>
 - non-Catalyst-dependent modules being written with Moose as the lingua
 franca, and then thin glue to integrate them into Catalyst (or in the
 case of FormHandler, no glue required at all :).
@@ -144,7 +144,7 @@
 objects which will enable a whole bunch more awesome things, and miyagawa's
 Catalyst::Engine::PSGI lets us take advantage of Plack - which I fully expect
 to take the perl web world by storm in the next year. I might even manage to
-figure out how some of the things I've been experimenting with in Web::Simple
+figure out how some of the things I've been experimenting with in L<Web::Simple>
 apply to improving the state of the art rather than just sitting around talking
 design with people and writing waffling articles.