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 15: Line 15:
* {{l/ver/class|cDropinLink}}
* {{l/ver/class|cDropinLink}}
==Methods==
==Methods==
* <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>{{l/sub|Run}}()</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> sends a {{l/ver/class|cEventNodeBuild}} event
** <code>{{l/sub|DoBuilding}}()</code> sends a {{l/ver/class|cEventNodeBuild}} event
** <code>DoFiguring()</code> sends a {{l/ver/class|cEventNodeFigure}} event
** <code>{{l/sub|DoFiguring}}()</code> sends a {{l/ver/class|cEventNodeFigure}} event
** <code>DoOutput()</code> sends a {{l/ver/class|cEventNodeRender}} event, and echoes its output to the display.
** <code>{{l/sub|DoOutput}}()</code> sends a {{l/ver/class|cEventNodeRender}} event, and echoes its output to the display.

Latest revision as of 15:32, 17 December 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.

What generally triggers the need to do anything besides render the default page is when the event-propagation reaches an element that responds to input of some kind from the user. Input can either be received as POST/GET data or as part of the site-relative URI. Feature-selection is most commonly invoked from URI data, while POST/GET data is generally expected by specific features.

Classes that receive URI data include:

Methods