Ferreteria/v0.6: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:
{| class="wikitable sortable"
{| class="wikitable sortable"
! namespace || endname
! namespace || endname
{{fmt/row/clade|Woozalia\Ferret\Aux|StandardBase}}
{{fmt/row/clade|Woozalia\Ferret\Aux|StandardBase}}   || standard base class with diagnostic services
{{fmt/row/clade|Woozalia\Ferret\Config|Objectorium}}
{{fmt/row/clade|Woozalia\Ferret\Config|Objectorium}} || object registry
{{fmt/row/clade|Woozalia\Ferret\Sys\Events\Actor|Option}}
{{fmt/row/clade|Woozalia\Ferret\Sys\Events|InputReq}} || input requests
{{fmt/row/clade|Woozalia\Ferret\Sys\Events|Actor}}
{{fmt/row/clade|Woozalia\Ferret\Sys\Data\reqs\Engine|AdminRq}} || administration request to a DB engine
{{fmt/row/clade|Woozalia\Futil\Sys\dba|Actor}}
{{fmt/row/clade|Woozalia\Ferret\Sys\Data\reqs\Engine|CommRq}} ||  communication request to a DB engine
{{fmt/row/clade|Woozalia\Ferret\Sys\Events|Action}}
{{fmt/row/clade|Woozalia\Futil\Sys\dba|InReq}}       || futilities: DBA-specific input requests
|}
|}


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:
==Subsystems==
* Actor handles UI interactions: interpret the input, output feedback for the user.
* {{l/sub|pfx=system/|Input Requests}}
* 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 21:00, 10 March 2025

Clade Documentation

namespace endname
Woozalia\Ferret\Aux StandardBase standard base class with diagnostic services
Woozalia\Ferret\Config Objectorium object registry
Woozalia\Ferret\Sys\Events InputReq input requests
Woozalia\Ferret\Sys\Data\reqs\Engine AdminRq administration request to a DB engine
Woozalia\Ferret\Sys\Data\reqs\Engine CommRq communication request to a DB engine
Woozalia\Futil\Sys\dba InReq futilities: DBA-specific input requests

Subsystems