Ferreteria/v0.5/@cls/caWebPage: Difference between revisions

From Woozle Writes Code
< Ferreteria‎ | v0.5‎ | @cls
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:
This is a singleton class. It expects the main App object to call <code>DoAllEvents</code>, which then runs the event-sequence needed to process input and generate an output page with the appropriate contents.
This is a singleton class. It expects the main App object to call <code>DoAllEvents</code>, which then runs the event-sequence needed to process input and generate an output page with the appropriate contents.
==Methods==
==Methods==
* <code>DoAllEvents</code> calls the following:
* <code>DoAllEvents</code> calls the following, which each in turn create an Event object and start it propagating by passing it to {{l/ver/meth|layout/event|OnEvent}} (used by the {{l/ver|layout/event}} subsystem):
** <code>DoBuilding()</code> creates and propagates a {{l/ver/class|cEventNodeBuild}} event
** <code>DoBuilding()</code> sends a {{l/ver/class|cEventNodeBuild}} event
** <code>DoFiguring()</code> creates and propagates a {{l/ver/class|cEventNodeFigure}} event
** <code>DoFiguring()</code> sends a {{l/ver/class|cEventNodeFigure}} event
** <code>DoOutput()</code> creates and propagates a {{l/ver/class|cEventNodeRender}} event, and echoes its output to the display.
** <code>DoOutput()</code> sends a {{l/ver/class|cEventNodeRender}} event, and echoes its output to the display.

Revision as of 16:04, 25 July 2022

class ferret\layout\caWebPage
cElement caWebPage caHypertextPage

Startup

This is a singleton class. It expects the main App object to call DoAllEvents, which then runs the event-sequence needed to process input and generate an output page with the appropriate contents.

Methods

  • DoAllEvents calls the following, which each in turn create an Event object and start it propagating by passing it to OnEvent() (used by the layout/event subsystem):