Ferreteria/v0.5/startup
|
Ferreteria startup process
|
This is the chain of events that takes place, in a typical application based on caAppUser ("the App object" or just "App"), when the site is invoked (i.e. a page is requested, possibly just the front page or possibly something more specific).
Assuming there are no initialization problems, App calls its Main() function. This then opens the database and, if successful, calls its GetPageObject() method to get the Page object to use for rendering. The class to used is determined by the Ferreteria deployment's configuration, and is not (at least by default) affected by the URI data.
App->Main() then calls the Page object's DoBuilding(), DoFiguring(), and DoOutput() methods. Each of those then creates an appropriate evint object and passes it to $this->DoEvent():
- DoBuilding(): cEventNodeBuild
- DoFiguring(): cEventNodeFigure
- DoOutput() cRender
documentation in progress
Changes
- 2022-06-22 DoOutput() now also uses the evint system. Subsidiary classes need revision to be in line with this.
- WAS: DoOutput() actually calls $this->Render() which calls $this->RenderNodes() which must be defined by the Page object. The standard implementation is to use the tRenderableTree trait, which then iterates through each sub-node... this doesn't quite make sense. At what point is the Render event created?
- cEvent* classes should be renamed to remove the redundant "Event", since they're already in the ferret\evint namespace (...or possibly all the events should be in the ferret\page namespace...)