Commit | Line | Data |
1f9daa1e |
1 | =head1 NAME |
2 | |
3 | Reaction::Manual::Intro - Introduction to Reaction |
4 | |
5 | =head1 INTRODUCTION |
6 | |
7 | Reaction is basically an extended MVC: |
8 | |
9 | =over |
10 | |
11 | =item Domain Model |
12 | |
13 | DBIC schema, etc. |
14 | |
15 | =item Interface Model |
16 | |
17 | Model::DBIC::Schema and Action classes. |
18 | |
19 | =item Controller |
20 | |
21 | Mediation and navigation. |
22 | |
23 | =item ViewPort |
24 | |
25 | View logic and event handling encapsulation. |
26 | |
27 | =item Renderer |
28 | |
29 | View:: classes, handed viewports. |
30 | |
31 | =back |
32 | |
33 | =head1 THE REACTION WAY |
34 | |
35 | The idea is you separate your domain model, which encapsulates the domain |
996236fb |
36 | itself, from your interface model, which is a model of how a particular app or |
1f9daa1e |
37 | class of apps interact with that domain and provides objects/methods to |
38 | encapsulate the common operations it does. |
39 | |
40 | =head2 Basic usage |
41 | |
42 | XXX TODO |
43 | |
44 | =head1 SEE ALSO |
45 | |
46 | =over |
47 | |
48 | =item * L<Reaction::Manual::Cookbook> |
49 | |
50 | =item * L<Reaction::Manual::FAQ> |
51 | |
52 | =back |
53 | |
54 | =head1 AUTHORS |
55 | |
56 | See L<Reaction::Class> for authors. |
57 | |
58 | =head1 LICENSE |
59 | |
60 | See L<Reaction::Class> for the license. |
61 | |
62 | =cut |