Ferreteria/v0.5/portrow/disp: Difference between revisions
< Ferreteria | v0.5 | portrow
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{fmt/title|PortRow Display class}} | |||
{| | {| | ||
|- | |- | ||
| Line 7: | Line 8: | ||
{{l/ver|PortRow/stor|Storage}} | {{l/ver|PortRow/stor|Storage}} | ||
|} | |} | ||
'''code''': {{l/ferreteria/code|data/fields/rows/display/display.php}}, {{l/ferreteria/code|data/fields/rows/display/display.bimode.php}} | * '''code''': <s>{{l/ferreteria/code|data/fields/rows/display/display.php}}, {{l/ferreteria/code|data/fields/rows/display/display.bimode.php}}</s> | ||
* '''related''': {{l/ver|PortCard/disp|PortCard display class}}, {{l/ver|Feature/rendering|Feature rendering}} | |||
==About== | ==About== | ||
As with the {{l/ver|PortCard/disp|PortCard display}} classes, the PortRow display classes handle user I/O formats; see {{l/ver|PortCard/disp}} for additional details. | As with the {{l/ver|PortCard/disp|PortCard display}} classes, the PortRow display classes handle user I/O formats; see {{l/ver|PortCard/disp}} for additional details. | ||
| Line 15: | Line 17: | ||
(listing not necessarily complete) | (listing not necessarily complete) | ||
* Events: | * Events: | ||
** '''OnCreateElements( | ** '''OnCreateElements({{l/ver/class|caEvent}} $oe)''' : void | ||
** '''OnRunCalculations( | ** '''OnRunCalculations({{l/ver/class|caEvent}} $oe)''' : void | ||
** '''Render( | ** '''Render({{l/ver/class|caEvent}} $oe)''' : void ('''Note''' 2022-07-10: This may now be incorrect.) | ||
* Config: | * Config: | ||
** '''CardClass()''' : string | ** '''CardClass()''' : string | ||
Latest revision as of 18:04, 10 July 2022
|
PortRow Display class
|
| Navigation: PortBank : PortRow : |
- code:
data/fields/rows/display/display.php, data/fields/rows/display/display.bimode.php - related: PortCard display class, Feature rendering
About
As with the PortCard display classes, the PortRow display classes handle user I/O formats; see PortCard/disp for additional details.
There is a dual subclass for handling cases where we want to be able to display either single records as a page or multiple records.
Required Methods
(listing not necessarily complete)
- Events:
- Config:
- CardClass() : string
- ContentTemplateString() : string - must return a string template which shows how a given row's data should be presented
Thinking
The templating system is managed by the Rows classes rather than Card classes because we don't want to be creating the Template object over and over again when we're displaying multiple rows. Once you establish that, then it also makes sense for the template string to be defined by the (Display) Rows class as well.