a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Revision history for Reaction
0.002005 - 8 Mar 2011
- use JSON instead of JSON::Any
0.002004 - 5 Mar 2011
- add a warning for people not using Reaction::Role(::Parameterized)
- silence m2m warnings during tests
0.002003 - 4 Mar 2011
- fixes for Moose 2
0.002002 - 5 Nov 2010
- use JSON::Any instead of JSON
0.002001 - 2 Nov 2010
- Fix some POD and tests
- Fix Order role to allow for exclusions (for non-indexed columns) and
coerceion of the column name to allow proper ORDER BY generation in
belongs_to rels and fields that do not map directly to columns.
- Fix Package names in POD for various files. this was causing some
weirdness in CPAN.
- All Reaction::UI::ViewPort::* now uses MooseX::Types
- Add 'action' attribute to Action viewport
- Adapt widget and layout to changes
- Add example of explicitly stating action to ComponentUI
- Don't override custom location in push_viewport
- Wire layout_args, which was forgotten + example of how to use it
- CRUD functionality is now implemented as roles, so it can be used
without needing to use Controller::Collection::CRUD
- Deprecate redirect_to and move it to an external role
- Controllers no longer 'use Reaction::Class' which was causing
problems with metaclass compatibility. 'use Moose' is now the
preferred approach.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Collection.
Reaction is a Catalyst extension providing you with:
- Model mutations abstracted into Action objects.
- Reflection to generate interface models using the Action objects
from a DBIx::Class schema.
- An abstract UI expression system based on view, skin, rendering
context, widget and layout set.
- Stylable via skins. Parts of the skins can be extended and flexibly
from large down to very small parts.
- Full separation of interface rendering structure and templating,
making re-usable extensions even easier.
