CGI::MxScreen::Screen CGI::MxScreen::Screen is the ancestor for all user screens.
Download

CGI::MxScreen::Screen Ranking & Summary

CGI::MxScreen::Screen Tags

Perl module cgi perl CGI MxScreen MxScreen

CGI::MxScreen::Screen Description

CGI::MxScreen::Screen is the ancestor for all user screens. CGI::MxScreen::Screen is the ancestor for all user screens.SYNOPSIS use base qw(CGI::MxScreen::Screen); sub display { # display screen -- defined my $self = shift; my ($arg1, $arg2) = @_; ... }This deferred class is meant to be the ancestor of all your application screens. You must inherit from CGI::MxScreen::Screen and at least define the display() routine, which will be called by the CGI::MxScreen manager when that screen is selected for display.CGI::MxScreen::Screen objects are blessed hashes. In order to leave you as much of the key namespace as possible, all attributes defined by the deferred class start with two leading underscores. Contrary to the routine namespace (see "INTERFACE" below), this simple workaround should prevent any accidental attribute collision.Screen objects must be serializable. That means they must never hold or refer to objects or data containing things known to be non-serializable, like GLOB and CODE references.Screen objects are never created by the user. They are handled by the CGI::MxScreen manager, who will ensure that at most one instance of each screen name will be created during a session. That means the init() routine will be called at most once. I say at most because screens are created on demand, and if your application does not need to show some state during a session, then the screen object will never be created. Requirements: · Perl

CGI::MxScreen::Screen Related Software