[Jifty-commit] r2771 - in jifty/trunk/lib/Jifty: .
jifty-commit at lists.jifty.org
jifty-commit at lists.jifty.org
Fri Feb 9 04:37:27 EST 2007
Date: Fri Feb 9 04:37:25 2007
New Revision: 2771
lib/Jifty/Plugin.pm - typo fix
lib/Jifty/Manual/Tutorial.pod - cleanup, linked a pod reference
lib/Jifty/Manual/Cookbook.pod - spelling and grammar
--- jifty/trunk/lib/Jifty/Manual/Cookbook.pod (original)
+++ jifty/trunk/lib/Jifty/Manual/Cookbook.pod Fri Feb 9 04:37:25 2007
@@ -181,7 +181,7 @@
dispatcher, to limit who is able to perform what actions -- see
-=head2 Run my Jifty app as fascgi in Apache/Lighttpd ?
+=head2 Run my Jifty app as fastcgi in Apache/Lighttpd ?
Jifty provides a really simple way to run the application as a fastcgi
server. The complete instructions and examples are in C<'jifty help
@@ -259,7 +259,7 @@
If the form is generated by a C<Jifty::Action::Record>-based action
(all those autogenerated CRUD actions), then this is all you need to
-do. And that is probably 90% of the case. C<Jifty::Action::Record>
+do. And that is probably 90% of cases. C<Jifty::Action::Record>
would check if there is a method named like C<canonicalize_fieldname>
generated. You do not have to modify any code in your view. Jifty does
--- jifty/trunk/lib/Jifty/Manual/Tutorial.pod (original)
+++ jifty/trunk/lib/Jifty/Manual/Tutorial.pod Fri Feb 9 04:37:25 2007
@@ -30,11 +30,10 @@
modules your system needs, and downloading and installing them all in
one go. Don't worry, it will ask you first before it makes any changes.
-On most systems you can Perl's bundled CPAN module to download
+On most systems you can use Perl's bundled CPAN module to download
and install Jifty:
- # perl -MCPAN -e'install Jifty' # Unix-like systems
- # perl -MCPAN -e"install Jifty" # Win32 systems
+ # perl -MCPAN -e"install Jifty"
If you've downloaded a C<.tar.gz> of Jifty, you can do a
@@ -55,9 +54,9 @@
Once you have Jifty happily installed, you're ready to
create your first application.
-Jifty is intentionally a bit minimalist. All you I<really>
-need to make an application go is a copy of the F<jifty> commandline
-tool (inside your new application's F<bin/> directory.
+Jifty is intentionally a bit minimalist. All you I<really> need to make
+an application go is a copy of the F<jifty> commandline tool (inside
+your new application's F<bin/> directory.)
Of course, it's often helpful to have a bit more structure around to
help guide your work. Jifty comes with tools to build that structure for
@@ -240,7 +239,7 @@
Ok. It's time to initialize MyWeblog's database. By default, Jifty sets up your
application with the SQLite database engine. If you'd rather use PostgreSQL or
-MySQL, you need to add some content to F<etc/jifty.yml>. (See C<Jifty::Config>
+MySQL, you need to add some content to F<etc/jifty.yml>. (See L<Jifty::Config>
for a bit more information).
# jifty schema --setup
--- jifty/trunk/lib/Jifty/Plugin.pm (original)
+++ jifty/trunk/lib/Jifty/Plugin.pm Fri Feb 9 04:37:25 2007
@@ -25,7 +25,7 @@
The dispatcher for a plugin should live in
-C<Jifty::Plugin::I<name>::Disptcher>; it is written like any other
+C<Jifty::Plugin::I<name>::Dispatcher>; it is written like any other
L<Jifty::Dispatcher>. Plugin dispatcher rules are checked before the
application's rules; however, see L<Jifty::Dispatcher/Plugins and rule
ordering> for how to manually specify exceptions to this.
More information about the Jifty-commit