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 if exists($params{only_if}) && !$params{only_if};
29 return if exists($params{not_if}) && $params{not_if};
30 return SL::Layout::ActionBar::Submit->new(text => $text, params => \%params);
35 # shortcut for presenter
45 # unique id to tie div and javascript together
47 $_[0]->params->{id} //
48 $_[0]->p->name_to_id('action[]')
58 planned options for clickables:
60 - checks => [ ... ] (done)
62 a list of functions that need to return true before submitting
64 - submit => [ form-selector, { params } ] (done)
66 on click submit the form specified by form-selector with the additional params
68 - function => function-name (done)
70 on click call the specified function (is this a special case of checks?)
72 - disabled => true/false/tooltip explaning why disabled (done)
76 - runtime disable/enable