Difference between revisions of "How to make a Screen perform Actions"

From EPrints Documentation
Jump to: navigation, search
(Processing the actions)
(Getting actions recognised)
Line 72: Line 72:
 
       = [qw/new edit cancel view netunlink netlink repounlink repolink/];
 
       = [qw/new edit cancel view netunlink netlink repounlink repolink/];
  
   $self->{appears} = [
+
   $self->{appears} = .....
    { place    => "admin_actions_editorial",
+
      position => 1000,
+
    },
+
  ];
+
  
 +
  ## any other code.....
 +
 
   return $self;
 
   return $self;
 
} ## end sub new
 
} ## end sub new

Revision as of 08:31, 23 April 2010

Works in EPrints 3.2+

Please read the page on How_to_make_a_Screen_for_the_Admin_Section as this extends that information.

NOTE: in this page, $s is the session or repository object, and $f is the (x)html DOM fragment

What's happening

The process has four parts:

  1. Some action buttons
  2. Some action routines
    1. A allow routine
    2. An action routine
      1. These routines could all be contained in the one package
      2. These routines could be spread out over several packages
  3. Where to go after the action completes

Making the buttons

The action buttons are the functionality that make the work... well, flow.

You need to define the "screen" (perl package) that contains the actions, and what the actions are.

The $s->render_action_buttons function takes a hash, which describes the set of buttons to display:

    my %buttons = (
		    cancel   => $self->phrase( "action:cancel:title" ), # Is defined as "Cancel"
                    update   => $self->phrase( "action:update:title" ), # Is defined as "Update"
                    _order   => [ "update", "cancel" ],
                    _class   => "ep_form_button_bar"
	          );
    $f->appendChild( $s->render_action_buttons( %buttons ) );
  • cancel => $self->phrase( "action:cancel:title" ) describe one action button: the internal name for the action and the text to be used for that button. You may have any number of buttons.
  • _order is a reference to a list defining the order for the buttons. With nothing defined, the order will be random.
  • _class defines the css class to give to the div that contains the buttons.

The above code would produce the following (x)html:

<div class="ep_form_button_bar">
 <input type="submit" class="ep_form_action_button"
        onclick="return EPJS_button_pushed( '_action_update' )"
        name="_action_update" value="Update">
 <input type="submit" class="ep_form_action_button"
        onclick="return EPJS_button_pushed( '_action_cancel' )"
        name="_action_cancel" value="Cancel">
 </div>

Where the actions are processed

The actions are processed in a "Screen", a perl package. The form being submitted therefor needs to contain a reference to that package:

   $f->appendChild( $s->render_hidden_field( "screen", "Orgs"));

This would call the package EPrints::Plugin::Screen::Orgs, and try to process the selected action in there

(Yes, this means that one can have the same action in multiple Screens, as well as multiple action in the same Screen)

Processing the actions

The EPrints processor system calls a specified action in a named package (as detailed above)

Getting actions recognised

Before a Screen will even consider processing an action, it need to register those actions with the system. This is defined in $self->{actions} in the new method:

sub new {
  my ( $class, %params ) = @_;

  my $self = $class->SUPER::new(%params);

  $self->{actions}
      = [qw/new edit cancel view netunlink netlink repounlink repolink/];

  $self->{appears} = .....

  ## any other code.....
 
  return $self;
} ## end sub new


There are two functions needed: allow_action and action_action... where action is the key given in the buttons hash above.

The allow test

The EPrints processor will always test to see if the user is permitted to perform an action. A "True" return will permit the action.

sub allow_cancel 
{
   return 1; # everyone can do this "cancel" action
}

sub allow_update
{
    my( $self ) = @_;
    return $self->can_edit; # Only users who have "can_edit" permissions can do this "update" action
}

The actual action routines

Assuming that the user is permitted to do the action, then EPrints processor will call the appropriate action routine:

sub action_cancel
{
    my( $self ) = @_;

    # Do stuff

}

Getting the parameters

The parameters are collected from the session:

 my $oname = $self->{session}->param( 'oarj_oname' );

One could be a bit more conservative:

  my %params;

  # Have we got any parameters (should be a yes, actions are set in parameters)
  if ($self->{session}->have_parameters)
  {

     # Get a list of all the parameters passed in
     my @param_list = $self->{session}->param;

     # build up a hash of all the parameters
     foreach my $p (@param_list) {
        $params{$p} = $self->{session}->param( $p );
     }
  };

.... of course one would assume that, having written the action handler, you know what parameters to expect, and can just ask for them directly!

Where to go after the action completes

By default, the EPrints processor will then render whatever's in the render routine for the package that the action routines are in. If you want the EPrints processor to use a different package to render something to the page, then:

sub action_cancel
{
    my( $self ) = @_;

    # Do stuff
    $self->{processor}->{screenid} = "My::Package";
}

will call the render routine in the package EPrints::Plugin::Screen::My::Package


Return to the main Screen_Plugins page.