1 package SL::Layout::ActionBar::Action;
4 use parent qw(Rose::Object);
7 require SL::Layout::ActionBar::Submit;
9 use Rose::Object::MakeMethods::Generic (
10 'scalar --get_set_init' => [ qw(id params text) ],
13 # subclassing interface
16 die 'needs to be implemented';
20 sprintf q|$('#%s').data('action', %s);|, $_[0]->id, JSON->new->allow_blessed->convert_blessed->encode($_[0]->params);
23 # this is mostly so that outside consumer don't need to load subclasses themselves
25 my ($class, $data) = @_;
27 my ($text, %params) = @$data;
28 return SL::Layout::ActionBar::Submit->new(text => $text, params => \%params);
31 # shortcut for presenter
41 # unique id to tie div and javascript together
43 $_[0]->params->{id} //
44 $_[0]->p->name_to_id('action[]')
54 planned options for clickables:
56 - checks => [ ... ] (done)
58 a list of functions that need to return true before submitting
60 - submit => [ form-selector, { params } ] (done)
62 on click submit the form specified by form-selector with the additional params
64 - function => function-name (done)
66 on click call the specified function (is this a special case of checks?)
68 - disabled => true/false/tooltip explaning why disabled (done)
72 - runtime disable/enable