X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FIntro.pod;h=3cdaff079bfb4dfbf17867371fea3733193ab7e4;hp=941c021474676c69936429f965e382e37b853c53;hb=792ad33189eba7c10dd2d2222301481256a1959c;hpb=089747172705c7ecb4dfac88c6e3b09f8c48e672 diff --git a/lib/Catalyst/Manual/Intro.pod b/lib/Catalyst/Manual/Intro.pod index 941c021..3cdaff0 100644 --- a/lib/Catalyst/Manual/Intro.pod +++ b/lib/Catalyst/Manual/Intro.pod @@ -14,17 +14,17 @@ with Catalyst, see L. =head2 What is Catalyst? Catalyst is an elegant web application framework, extremely flexible -yet extremely simple. It's similar to Ruby on Rails, Spring (Java), -and L, upon which it was originally based. Its most important -design philosphy is to provide easy access to all the tools you need -to develop web applications, with few restrictions on how you need to -use these tools. However, this does mean that it is always possible to -do things in a different way. Other web frameworks are B -simpler to use, but achieve this by locking the programmer into a -single set of tools. Catalyst's emphasis on flexibility means that you -have to think more to use it. We view this as a feature. For example, -this leads to Catalyst being more suited to system integration tasks -than other web frameworks. +yet extremely simple. It's similar to Ruby on Rails, Spring (Java), and +L, upon which it was originally based. Its most +important design philosphy is to provide easy access to all the tools +you need to develop web applications, with few restrictions on how you +need to use these tools. However, this does mean that it is always +possible to do things in a different way. Other web frameworks are +I simpler to use, but achieve this by locking the programmer +into a single set of tools. Catalyst's emphasis on flexibility means +that you have to think more to use it. We view this as a feature. For +example, this leads to Catalyst being more suited to system integration +tasks than other web frameworks. =head3 MVC @@ -216,14 +216,15 @@ means that this decision is entirely up to you, the programmer; Catalyst doesn't enforce anything. See L for a general discussion of these issues. -All components must inherit from L, which provides a -simple class structure and some common class methods like C and -C (constructor). +Model, View and Controller components must inherit from L, +L and L, respectively. These, in turn, inherit +from L which provides a simple class structure and some +common class methods like C and C (constructor). package MyApp::Controller::Catalog; use strict; - use base 'Catalyst::Base'; + use base 'Catalyst::Controller'; __PACKAGE__->config( foo => 'bar' ); @@ -330,7 +331,7 @@ But first, we need a database. INSERT INTO foo (data) VALUES ('TEST!'); - % sqlite /tmp/myapp.db < myapp.sql + % sqlite3 /tmp/myapp.db < myapp.sql Now we can create a DBIC::Schema model for this database. @@ -819,11 +820,16 @@ dispatch type, please see L. sub foo : Private { } Matches no URL, and cannot be executed by requesting a URL that -corresponds to the action key. Catalyst's :Private attribute is exclusive -and doesn't work with other attributes. Private actions can be executed -only inside a Catalyst application, by calling the C method: +corresponds to the action key. Catalyst's :Private attribute is +exclusive and doesn't work with other attributes (so will not work +combined with Path or Chained attributes). With the exception of the +C< index >, C< auto > and C< default > actions, Private actions can +only be executed from inside a Catalyst application, by calling the +C or C methods: $c->forward('foo'); + # or + $c->detach('foo'); See L for a full explanation of C. Note that, as discussed there, when forwarding from another component, you must use @@ -1159,8 +1165,8 @@ IRC: Mailing lists: - http://lists.rawmode.org/mailman/listinfo/catalyst - http://lists.rawmode.org/mailman/listinfo/catalyst-dev + http://lists.scsys.co.uk/mailman/listinfo/catalyst + http://lists.scsys.co.uk/mailman/listinfo/catalyst-dev =head1 AUTHOR