Ferreteria/v2/usage/pages: Difference between revisions
< Ferreteria | v2 | usage
Jump to navigation
Jump to search
(basic stuff) |
(pages do not like thistles or hunny) |
||
| Line 3: | Line 3: | ||
An application will generally create their own page class descended from one of these classes, depending on what functionality it wants. | An application will generally create their own page class descended from one of these classes, depending on what functionality it wants. | ||
Pages do not do URL translation; that is handled by {{l/same|menus}}. | |||
==Files== | ==Files== | ||
* {{ferreteria/code|page.php}} | * {{ferreteria/code|page.php}} | ||
Revision as of 22:23, 16 February 2015
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.
Pages do not do URL translation; that is handled by menus.
Files
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
- clsPageBasic (abstract) - handles exception-email generation