Ferreteria/v0.5/@cls/caWebPage: Difference between revisions
< Ferreteria | v0.5 | @cls
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
==Startup== | ==Startup== | ||
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. | ||
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: | |||
* {{l/ver/class|cDropinLink}} | |||
==Methods== | ==Methods== | ||
* <code> | * <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> | ** <code>{{l/sub|DoBuilding}}()</code> sends a {{l/ver/class|cEventNodeBuild}} event | ||
** <code>DoFiguring()</code> | ** <code>{{l/sub|DoFiguring}}()</code> sends a {{l/ver/class|cEventNodeFigure}} event | ||
** <code>DoOutput()</code> | ** <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
| cElement → | caWebPage → | caHypertextPage |
- Source: layout/page/1.php
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
Run()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):DoBuilding()sends a cEventNodeBuild eventDoFiguring()sends a cEventNodeFigure eventDoOutput()sends a cEventNodeRender event, and echoes its output to the display.