Catalyst makes it easy to do all of these tasks, and many more. It is
extremely flexible in terms of what it allows you to do, and very fast.
-It has a very large number of "plugins" that interact with existing Perl
+It has a large number of "components" and "plugins" that interact with existing Perl
modules so that you can easily use them from within your
-application.
+application.
=over 4
-=item * Interact with a web server?
+=item * Interact with a web server?
Catalyst lets you use a number of different ones, and even comes with a
built-in server for testing or local deployment.
-=item * Do something based on a URI?
+=item * Do something based on a URI?
Catalyst has extremely flexible systems for figuring out what to do
based on a URI.
Catalyst has many plugins for different databases and database
frameworks, and for other non-database storage systems.
-=item * Handle forms?
+=item * Handle forms?
Catalyst has plugins available for several form creation and validation
systems that make it easy for the programmer to manage.
Catalyst has plugins available for a number of template modules and
other output packages.
-=item * Manage users?
+=item * Manage users?
Catalyst has plugins that handle sessions, authentication, and
authorization, in any way you need.
-=item * Developing the application?
+=item * Developing the application?
Catalyst has detailed logging built-in, which you can configure as
necessary, and supports the easy creation of new tests--some of which
easy development of powerful web databases; L<Jifty>, which does a great
deal of automation in helping to set up web sites with many complex
features; and Ruby on Rails (see L<http://www.rubyonrails.org>), written
-of course in Ruby and among the most popular web development systems. Is
-it not the purpose of this document to criticize or even briefly
+of course in Ruby and among the most popular web development systems. It
+is not the purpose of this document to criticize or even briefly
evaluate these other frameworks; they may be useful for you and if so we
encourage you to give them a try.
gluing some other module into Catalyst; the display logic is written
within the template itself.
-The Controller is Catalyst itself. When a request is made to Catalyst,
+The B<Controller> is Catalyst itself. When a request is made to Catalyst,
it will be received by one of your Controller modules; this module
will figure out what the user is trying to do, gather the necessary
data from a Model, and send it to a View for display.
then generate an HTML page, which Catalyst will send to the user's
browser, using whatever web server you've configured.
-How does this help you?
+=head3 How does this help you?
In many ways. Suppose you have a small catalog now, and you're using a
lightweight database such as SQLite, or maybe just a text file. But
rather than your Controller, is the better place to decide what to
display if you get an empty result). Catalyst just gives you the tools.
-=head1 AUTHOR
-
-Jesse Sheidlower, C<jester@panix.com>
-
=head1 SEE ALSO
L<Catalyst>, L<Catalyst::Manual::Intro>
+=head1 AUTHORS
+
+Catalyst Contributors, see Catalyst.pm
+
=head1 COPYRIGHT
-This program is free software, you can redistribute it and/or modify it
-under the same terms as Perl itself.
+This library is free software. You can redistribute it and/or modify it under
+the same terms as Perl itself.
+
+=cut
projects / catagits/Catalyst-Manual.git / blobdiff