File Coverage

blib/lib/ASP4/MasterPage.pm

Criterion	Covered	Total	%
statement	9	9	100.0
branch			n/a
condition			n/a
subroutine	3	3	100.0
pod			n/a
total	12	12	100.0

package ASP4::MasterPage;

use strict;
use warnings 'all';
use base 'ASP4::Page';

1;# return true:

=pod

=head1 NAME

ASP4::MasterPage - Root class for MasterPage classes.

=head1 SYNOPSIS

In your ASP script (C):

  <%@ MasterPage %>


      Default Heading

        Default Content




It gets compiled down to:

  package MyApp::_eg_master_asp;

  use strict;
  use warnings 'all';
  no warnings 'redefine';
  use base 'ASP4::MasterPage';
  use vars __PACKAGE__->VARS;
  use ASP4::PageLoader;

  sub _init {
    my ($s) = @_;
    $s->{script_name} = q;
    $s->{filename}    = q;
    $s->{base_class}  = q;
    $s->{compiled_as} = q;
    $s->{package}     = q;

    return;
  }

  sub run {
  use warnings 'all';
  my ($__self, $__context) = @_;
  #line 1
  ;$Response->Write(q~


      ~); $__self->heading($__context); $Response->Write(q~

        ~); $__self->content($__context); $Response->Write(q~



  ~);
  }

  sub heading {
  my ($__self, $__context) = @_;
  #line 4
  $Response->Write(q~Default Heading~);
  }# end heading

  sub content {
  my ($__self, $__context) = @_;
  #line 6
  $Response->Write(q~Default Content~);
  }# end content

  1;# return true:

Which, when executed, produces:



      Default Heading

        Default Content




=head2 But Wait - There's More!

MasterPages only get interesting when we add "child" pages to them:

(C)

  <%@ Page UseMasterPage="/eg-master.asp" %>

  New Heading

  New Content

Which compiles down to:

  package MyApp::_eg_child_asp;

  use strict;
  use warnings 'all';
  no warnings 'redefine';
  use base 'MyApp::_eg_master_asp';
  use vars __PACKAGE__->VARS;
  use ASP4::PageLoader;

  sub _init {
    my ($s) = @_;
    $s->{script_name} = q;
    $s->{filename}    = q;
    $s->{base_class}  = q;
    $s->{compiled_as} = q;
    $s->{package}     = q;
    $s->{masterpage}  = ASP4::PageLoader->load( script_name => q );
    return;
  }

  sub heading {
  my ($__self, $__context) = @_;
  #line 3
  $Response->Write(q~New Heading~);
  }# end heading

  sub content {
  my ($__self, $__context) = @_;
  #line 5
  $Response->Write(q~New Content~);
  }# end content

  1;# return true:

And when executed produces:



      New Heading

        New Content




=head2 And Even More!

Child pages can also be master pages:

(C):

  <%@ MasterPage %>
  <%@ Page UseMasterPage="/eg-master.asp" %>

  New Heading


    New Content

      Copyright
      :
      All Rights Reserved



And inherited from again:

(C):

  <%@ Page UseMasterPage="/eg-master.asp" %>

  SuperMegaCorp, Inc.

Which - when executed, produces:



      New Heading


    New Content

      Copyright
      SuperMegaCorp, Inc.:
      All Rights Reserved






=head1 DESCRIPTION

MasterPages provide a means of rich page composition.  This means that instead
of a tangle of server-side includes, you can actually take advantage of this
new concept (came out decades ago) called "class inheritance" - and apply it
to your web pages.

=cut