Page classes are subclasses of , except for subclasses of . See the for the abstract page superclasses of the user interface. To make the default user interface use a page object of a different class, see how to specialize a page.
Page objects by default print a , a and a . Further composition depends on the PntPage subclass and its and . For changing the default composition of a page, see how to specialize a part of a page.
Pages are only meant for output. Form processing is done by . Depending on its result an action may or to a page for output.
There is a special for reporting errors to the user. Each should have a special skin for its as a startingpoint for browsing.
Pages are included, created and invoked by the object on the basis of the pntHandler request parameter. See the design documentation about request dispatch. |
