1 package Reaction::UI::ViewPort::Role::Actions;
4 use Reaction::UI::ViewPort::URI;
6 use namespace::clean -except => [ qw(meta) ];
19 has action_filter => (
20 isa => 'CodeRef', is => 'ro',
23 has action_prototypes => (
30 has computed_action_order => (
36 sub _build_computed_action_order {
38 my $ordered = $self->sort_by_spec(
39 ($self->has_action_order ? $self->action_order : []),
40 [ keys %{ $self->action_prototypes } ]
42 return $self->has_action_filter ?
43 $self->action_filter->($ordered, $self->model) : $ordered;
50 my $loc = $self->location;
51 my $target = $self->model;
53 foreach my $proto_name ( @{ $self->computed_action_order } ) {
54 my $proto = $self->action_prototypes->{$proto_name};
55 my $uri = $proto->{uri} or confess('uri is required in prototype action');
56 my $label = exists $proto->{label} ? $proto->{label} : $proto_name;
57 my $layout = exists $proto->{layout} ? $proto->{layout} : 'uri';
59 my $action = Reaction::UI::ViewPort::URI->new(
60 location => join ('-', $loc, 'action', $i++),
61 uri => ( ref($uri) eq 'CODE' ? $uri->($target, $ctx) : $uri ),
62 display => ( ref($label) eq 'CODE' ? $label->($target, $ctx) : $label ),
63 layout => ( ref($layout) eq 'CODE' ? $layout->($target, $ctx) : $layout ),
76 Reaction::UI::ViewPort::Role::Actions
80 A role to ease attaching actions to L<Reaction::InterfaceModel::Object>s
86 Read-only, lazy-building ArrayRef of URI objects pointing to actions.
88 =head2 action_prototypes
90 A HashRef of prototypes for building the Action links. The prototypes should be
93 my %action_prototypes = (
94 example_action => { label => 'Example Action', uri => $uri_obj },
97 #or you can get fancy and do something like what is below:
99 my($im, $ctx) = @_; #InterfaceModel::Object/Collection, Catalyst Context
103 my($im, $ctx) = @_; #InterfaceModel::Object/Collection, Catalyst Context
104 return return $ctx->uri_for('some_action');
106 my %action_prototypes = (
107 example_action => { label => \&make_label, uri => \&make_uri },
112 User-provided ArrayRef with how the actions should be ordered eg
114 action_order => [qw/view edit delete/]
116 =head2 computed_action_order
118 Read-only lazy-building ARRAY ref. The final computed action order. This may
119 differ from the C<action_order> provided if you any actions were not included
124 =head2 _build_actions
126 Cycle through the C<computed_action_order> and create a new
127 L<ViewPort::URI|Reaction::UI::ViewPort::URI> object for each action using the
130 =head2 _build_computed_action_order
132 Compute the final action ordering by using the provided C<action_order> as a
133 spec to order all the present actions (the keys of C<action_prototypes>)
135 =head1 ACTION PROTOTYPES
137 Action prototypes are simply hashrefs that must contain a C<uri> key and may
138 contain a C<label> key. The label can be anything that the display attribute of
139 L<ViewPort::URI|Reaction::UI::ViewPort::URI> will accept, usually a scalar or a
140 ViewPort. The value for C<uri> may be either a scalar, a L<URI> object (or
141 anything that C<ISA URI>).
143 Additionally, both C<label> and C<uri> can be CODE refs. In this case, the code
144 will be executed at C<_build_actions> time and will recieve two arguments, the
145 value returned by C<model> and the value returned by C<ctx> in that order. Both
146 of these methods should be implemented in the consuming class. By convention,
147 model refers to the target of the action, an C<InterfaceModel::Object> in the
148 case of a member action and an C<InterfaceModel::Collection> in the case of a
149 Collection action. C<ctx> should be the current Catalyst context.
153 See L<Reaction::Class> for authors.
157 See L<Reaction::Class> for the license.