X-Git-Url: http://wagnertech.de/git?p=kivitendo-erp.git;a=blobdiff_plain;f=SL%2FClientJS.pm;fp=SL%2FClientJS.pm;h=49bde8092cbfbeb1114c5969ad9f93786a51a04f;hp=335bf8163107cdfcf383cd7c7e19a9de039d36cd;hb=53593baa211863fbf66540cf1bcc36c8fb37257f;hpb=deb4d2dbb676d7d6f69dfe7815d6e0cb09bd4a44 diff --git a/SL/ClientJS.pm b/SL/ClientJS.pm index 335bf8163..49bde8092 100644 --- a/SL/ClientJS.pm +++ b/SL/ClientJS.pm @@ -9,8 +9,8 @@ use SL::JSON (); use Rose::Object::MakeMethods::Generic ( - scalar => [ qw(controller) ], - 'scalar --get_set_init' => [ qw(_actions _flash _error) ], + scalar => [ qw() ], + 'scalar --get_set_init' => [ qw(controller _actions _flash _flash_detail _no_flash_clear _error) ], ); my %supported_methods = ( @@ -75,12 +75,12 @@ my %supported_methods = ( # ## jQuery UI dialog plugin ## pattern: $().dialog('') - # Opening and closing and closing a popup + # Opening and closing a popup 'dialog:open' => 1, # kivi.popup_dialog() 'dialog:close' => 1, # ## jQuery Form plugin ## - 'ajaxForm' => 1, # pattern: $().ajaxForm({ success: eval_json_result }) + 'ajaxForm' => 1, # $().ajaxForm({ success: eval_json_result }) # ## jstree plugin ## pattern: $.jstree._reference($()).() @@ -113,13 +113,18 @@ my %supported_methods = ( # ## other stuff ## redirect_to => 1, # window.location.href = + save_file => 4, # kivi.save_file(, ) flash => 2, # kivi.display_flash(, ) + flash_detail => 2, # kivi.display_flash_detail(, ) + clear_flash => 2, # kivi.clear_flash(, ) reinit_widgets => 0, # kivi.reinit_widgets() run => -1, # kivi.run(, ) run_once_for => 3, # kivi.run_once_for(, ) scroll_into_view => 1, # $()[0].scrollIntoView() + + set_cursor_position => 2, # kivi.set_cursor_position(, ) ); my %trim_target_for = map { ($_ => 1) } qw(insertAfter insertBefore appendTo prependTo); @@ -180,15 +185,23 @@ sub init__flash { return {}; } +sub init__flash_detail { + return {}; +} + sub init__error { return ''; } +sub init__no_flash_clear { + return ''; +} + sub to_json { my ($self) = @_; - return SL::JSON::to_json({ error => $self->_error }) if $self->_error; - return SL::JSON::to_json({ eval_actions => $self->_actions }); + return SL::JSON::to_json({ error => $self->_error }) if $self->_error; + return SL::JSON::to_json({ no_flash_clear => $self->_no_flash_clear, eval_actions => $self->_actions }); } sub to_array { @@ -236,6 +249,27 @@ sub flash { return $self; } +sub flash_detail { + my ($self, $type, @messages) = @_; + + my $message = join '
', grep { $_ } @messages; + + if (!$self->_flash_detail->{$type}) { + $self->_flash_detail->{$type} = [ 'flash_detail', $type, $message ]; + push @{ $self->_actions }, $self->_flash_detail->{$type}; + } else { + $self->_flash_detail->{$type}->[-1] .= ' ' . $message; + } + + return $self; +} + +sub no_flash_clear{ + my ($self) = @_; + $self->_no_flash_clear('1'); + return $self; +} + sub error { my ($self, @messages) = @_; @@ -244,6 +278,12 @@ sub error { return $self; } +sub init_controller { + # fallback + require SL::Controller::Base; + SL::Controller::Base->new; +} + 1; __END__ @@ -263,20 +303,15 @@ First some JavaScript code: // In the client generate an AJAX request whose 'success' handler // calls "eval_json_result(data)": var data = { - action: "SomeController/the_action", + action: "SomeController/my_personal_action", id: $('#some_input_field').val() }; $.post("controller.pl", data, eval_json_result); -Now some Perl code: - - # In the controller itself. First, make sure that the "client_js.js" - # is loaded. This must be done when the whole side is loaded, so - # it's not in the action called by the AJAX request shown above. - $::request->layout->use_javascript('client_js.js'); +Now some Controller (perl) code for my personal action: - # Now in that action called via AJAX: - sub action_the_action { + # my personal action + sub action_my_personal_action { my ($self) = @_; # Create a new client-side JS object and do stuff with it! @@ -315,7 +350,7 @@ This module enables the generation of jQuery-using JavaScript code on the server side. That code is then evaluated in a safe way on the client side. -The workflow is usally that the client creates an AJAX request, the +The workflow is usually that the client creates an AJAX request, the server creates some actions and sends them back, and the client then implements each of these actions. @@ -457,6 +492,17 @@ C on the same C<$self> will be merged by type. On the client side the flashes of all types will be cleared after each successful ClientJS call that did not end with C<$js-Eerror(...)>. +This clearing can be switched of by the function C + +=item C + +Display a detailed message C<$message> in the flash of type C<$type>. Multiple calls of +C on the same C<$self> will be merged by type. +So the flash message can be hold short and the visibility of details can toggled by the user. + +=item C + +No automatic clearing of flash after successful ClientJS call =item C @@ -614,7 +660,7 @@ C, C, C =head1 ADDING SUPPORT FOR ADDITIONAL FUNCTIONS -In order not having to maintain two files (this one and +In order to not have to maintain two files (this one and C) there's a script that can parse this file's C<%supported_methods> definition and generate the file C accordingly. The steps are: