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

From Woozle Writes Code
< Ferreteria‎ | v0.5‎ | @cls
Jump to navigation Jump to search
(Created page with "{{fmt/title|Ferreteria class <code>ferret\{{l/ver/class|layout}}\caEvent</code>}} {| style="border: solid 1px grey; background: #eef;" |- | {{l/ver/class|caEvent}} | &...")
 
No edit summary
 
Line 14: Line 14:
     abstract static public function Method() : string;  // method to call
     abstract static public function Method() : string;  // method to call
</syntaxhighlight>
</syntaxhighlight>
Abstracts for the methods defined by <code>Method()</code> in the three podling classes above are in {{l/ver/class|tExecutableTwig}}.
I'm not sure <code>Code()</code> makes sense. If we were ever going to log these events somewhere, it might -- but this class-family is designed just for internal state-propagating purposes.
I'm not sure <code>Code()</code> makes sense. If we were ever going to log these events somewhere, it might -- but this class-family is designed just for internal state-propagating purposes.

Latest revision as of 13:30, 21 July 2022

Ferreteria class ferret\layout\caEvent
caEvent

cEventNodeBuild
cEventNodeFigure
cEventNodeRender

Methods

    abstract static public function Code() : string;    // event-type name-string
    abstract static public function Method() : string;  // method to call

Abstracts for the methods defined by Method() in the three podling classes above are in tExecutableTwig.

I'm not sure Code() makes sense. If we were ever going to log these events somewhere, it might -- but this class-family is designed just for internal state-propagating purposes.