Ferreteria/v2/usage/pages

About

Pages in Ferreteria handle execution of various processes to build a page, including form input handling and rendering of output.

An application will generally create their own page class descended from one of these classes, depending on what functionality it wants.

When URL translation is needed from a Page object (e.g. ParsePath()), the object passes the request over to menus.

Files

• Template:Ferreteria/code

Classes

• clsPage (abstract) - default page execution, stub for automatic email when exception thrown; app, skin, and data objects
  • clsPageBasic (abstract) - handles exception-email generation
    • clsPageLogin (abstract) - provides login forms (inheritor must call them, though) and admin menus

Process

The basic sequence of page component creation as defined in clsPage is:

• $this->ParseInput();
• $this->HandleInput();
  • The application will typically implement this as something like:
    • $this->BuildMenu();
    • $this->MenuNode_Init();
    • $this->TitleString("Default Title");
    • $this->HandleContent();
  • This is kind of messy and needs to be mapped out and possibly redesigned.
• $this->PreSkinBuild();
• $this->Skin()->Build();

  // tell the skin to fill in its pieces

• $this->PostSkinBuild();
• $this->Skin()->DoPage();