Ferreteria/v0.6: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
(Created page with "==Clade Documentation== {| class="wikitable sortable" ! namespace || endname {{fmt/row/clade|Woozalia\Ferret\Aux|StandardBase}} {{fmt/row/clade|Woozalia\Ferret\Config|Objectorium}} {{fmt/row/clade|Woozalia\Ferret\Sys\Events\Actor|Option}} {{fmt/row/clade|Woozalia\Ferret\Sys\Events|Actor}} {{fmt/row/clade|Woozalia\Futil\Sys\dba|Actor}} {{fmt/row/clade|Woozalia\Ferret\Sys\Events|Action}} |}")
 
No edit summary
Line 9: Line 9:
{{fmt/row/clade|Woozalia\Ferret\Sys\Events|Action}}
{{fmt/row/clade|Woozalia\Ferret\Sys\Events|Action}}
|}
|}
2025-01-21 Okay, so, the problem with trying to combine Actor with Rq (mainly AdminRq) seems to be that they serve different parts of the transaction:
* Actor handles UI interactions: interpret the input, output feedback for the user.
* AdminRq handles comms between what the code knows it needs to do and the Engine objects that know how to do it.

Revision as of 02:05, 22 January 2025

Clade Documentation

namespace endname
Woozalia\Ferret\Aux StandardBase
Woozalia\Ferret\Config Objectorium
Woozalia\Ferret\Sys\Events\Actor Option
Woozalia\Ferret\Sys\Events Actor
Woozalia\Futil\Sys\dba Actor
Woozalia\Ferret\Sys\Events Action

2025-01-21 Okay, so, the problem with trying to combine Actor with Rq (mainly AdminRq) seems to be that they serve different parts of the transaction:

  • Actor handles UI interactions: interpret the input, output feedback for the user.
  • AdminRq handles comms between what the code knows it needs to do and the Engine objects that know how to do it.