This is the implementation of your business logic. An example would be a DBIx::Class schema providing you with collections, objects and relationships.
Your Domain Model will interface with Reaction through an Interface Model. Therefore your domain model itself can and should be decoupled from your Reaction application.
Whenever you push a ViewPort in your controller, you are pushing it onto the Focus Stack. When the root window (containing the root Focus Stack) is flushed by Reaction at the end of the request, the ViewPorts Widgets will be rendered inside each other.
A typical example would be a SiteLayout ViewPort being pushed onto the Focus Stack by your root action. A CRUD controller would then, if its list action was requested, push a ListView ViewPort. On flushing, the ListView will be rendered inside the SiteLayout.
Provides a standardized way for the application to interact with the Domain Models. It does this by providing objects, collections and actions.
Defines how a Widget fragment is rendered. They are organized in LayoutSets. Its arguments are provided by the Widget the LayoutSet specified.
Layout fragments reference other fragments and can be overridden or wrapped when the LayoutSet is an extension of another.
Contains Layouts. A LayoutSet is specified (or autodiscovered) for any ViewPort. It determines which Widget to use as the functional part used to render the ViewPort. A LayoutSet can also extend on another LayoutSet. With this, Layouts of the parent can be modified. This allows for very fine-grained control when developing different Skins.
The ListView Widget, ViewPort and LayoutSet group allows you to render an Interface Model collection as a table.
Model-View-Controller - a high-level software design pattern, which focuses on separation of concerns. For details on MVC, try here, here, and here. Reaction is an extended MVC system; it uses a two-layer Model (the Interface Model, with the Domain Model below it). Views are implemented by DOCTODO. Controllers are represented by DOCTODO.
DOCTODO: A software design pattern in which one
The context in which the Widgets rendering via the LayoutSet will be done. A typical example would be a Template Toolkit LayoutSet being used to render a Widget in the Reaction::UI::RenderingContext::TT context.
A Skin usually contains LayoutSets and files for static delivery. Since Skins are extendable and can be switched by configuration, they allow easy customization of your applications look and feel.
In Reaction, the View modules handle rendering the ViewPort. ViewPorts are the V in MVC.
Technically, the View creates the RenderingContext and finds the LayoutSets via the ViewPorts and Widgets from the LayoutSets that are required to render your page.
Represents a part of your web pages output. Your application creates a page by stacking ViewPorts referencing your Interface Models inside another. To each ViewPort belongs a LayoutSet, which will determine the layout and type of the Widgets rendering your page.
The functionality needed to render a part of your page. The Widget that is used is determined by the LayoutSet, which is in turn determined by the ViewPort.
The Widget organizes the layouts contained in the LayoutSet and provides them with data to render.
Please refer to these documents for further and more general information:
o Reaction::Manual o Reaction::Manual::Overview o Reaction::Manual::Intro
See Reaction::Class for authors.
See Reaction::Class for the license.
|perl v5.20.3||REACTION::MANUAL::GLOSSARY (3)||2010-10-29|