[Catalyst-commits] r12233 - trunk/examples/CatalystAdvent/root/2009

[jester at dev.catalyst.perl.org]

Author: jester
Date: 2009-12-07 14:21:21 +0000 (Mon, 07 Dec 2009)
New Revision: 12233

Modified:
   trunk/examples/CatalystAdvent/root/2009/7.pod
Log:
Light edits to Day 7 Advent


Modified: trunk/examples/CatalystAdvent/root/2009/7.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/7.pod	2009-12-07 13:52:28 UTC (rev 12232)
+++ trunk/examples/CatalystAdvent/root/2009/7.pod	2009-12-07 14:21:21 UTC (rev 12233)
@@ -7,16 +7,17 @@
 
 =head2 Application skeleton files are now in a sharedir
 
-The application skeleton files are now stored in a sharedir, making it much easier
-to alter / patch the content of generated applications. Component authors can
-also now use a sharedir, and the extra C<render_sharedir_file> method to
-get templatesd from a sharedir generated by their Helper class.
+The application skeleton files are now stored in a sharedir, making it
+much easier to alter / patch the content of generated
+applications. Component authors can also now use a sharedir, and can use
+the the extra C<render_sharedir_file> method to get templates from a
+sharedir generated by their Helper class.
 
 =head2 Scripts are now Classes
 
 The scripts, instead of being entities on their own, now just delegate the
 work to a C<< ScriptRunner >> class which finds a script class, loads it,
-makes an instance and invokes it's C<< ->run >> method.
+makes an instance, and invokes its C<< ->run >> method.
 
 If you open up a new script, you'll see something like
 this:
@@ -32,40 +33,41 @@
 
 =head2 What does this do for me?
 
-This means that fixing bugs in the scripts is significantly easier
-and less hassle for B<you>, as new scripts are included in L<Catalyst::Runtime>,
-therefore you get the benefit of them just by upgrading, rather than having
-to regenerate your scripts.
+This means that fixing bugs in the scripts is significantly easier and
+less hassle for B<you>, because new scripts are included in
+L<Catalyst::Runtime>. Therefore you get the benefit of them just by
+upgrading, rather than having to regenerate your scripts.
 
-Also, you can write custom scripts, or easily add options to the existing scripts.
-This is Really Good if you want to hack your own server
-with additional command line flags. If you create a class called
-C<< MyApp::Script::XXX >> then L<Catalyst::ScriptRunning> will pick it up
-and run it in favour of the built in script.
+Also, you can write custom scripts, or easily add options to the
+existing scripts.  This is Really Good if you want to hack your own
+server with additional command line flags. If you create a class called
+C<< MyApp::Script::XXX >>, then L<Catalyst::ScriptRunner> will pick it
+up and run it in favor of the built-in script.
 
-Authors of alternate engines should also be able to reuse L<Catalyst::ScriptRole>,
-provide a C<Catalyst::Script::> class and a C<Catalyst::Helper::> class, and
-then generate myapp_engine.pl scripts for the user which work just like the other
-scripts, without duplicating all of the script code..
+Authors of alternate engines should also be able to reuse
+L<Catalyst::ScriptRole>, provide a C<Catalyst::Script::> class and a
+C<Catalyst::Helper::> class, and then generate C<myapp_engine.pl> scripts
+for the user which work just like the other scripts, without duplicating
+all of the script code.
 
-L<Gitalist> is an example of an application already taking advantage of per-application
-scripts to provide a C<< --repo_dir >> option.
+L<Gitalist> is an example of an application already taking advantage of
+per-application scripts to provide a C<< --repo_dir >> option.
 
-=head2 Application skeleton now uses Moose.
+=head2 Application skeleton now uses Moose
 
-The generated application skeleton had been tidied up in a number of ways, and
+The generated application skeleton has been tidied up in a number of ways, and
 now generates applications which use L<Moose> and L<namespace::autoclean>,
-tests which use C< done_testing > and which turn off some deprecated features.
+tests which use C< done_testing >, and which turn off some deprecated features.
 
 That's all folks, short and simple. 
 
-Hopefully you'll think of some cool and
-fun uses for the new scripts and Helper code, and you'll blog in your Ironman blogs
-about them, or come chat to us in C< #catalyst-dev > about what you'd like to
-do if it doesn't seem obvious. 
+Hopefully you'll think of some cool and fun uses for the new scripts and
+Helper code, and you'll blog in your Ironman blogs about them, or come
+chat to us in C< #catalyst-dev > about what you'd like to do if it
+doesn't seem obvious.
 
 This new work is a good basis for people being able to do cool things, but
 I'm sure there is some work still to be done to make it easier when
 people start experimenting with their real life use-cases.
 
-- Devin "dhoss" Austin, and thanks a boat load to Tomas Doran for reviewing and beefing things up in this article.
+- Devin "dhoss" Austin, and thanks a boatload to Tomas Doran for reviewing and beefing things up in this article.