As a consequence of preceding experiments.. * I'll stick to the structure of the BufferProvider front-end interface * also the »code behind« will remain there; a purely abstract API has no merit here * however, the ''setup'' of the actual implementation will move into a derived class * this derived scope class, `BufferProviderSetup` will house two implementation classes * these two, now named `Stage` and `Store` provide the base implementation for the two "pillars" of the implementation Admitted, this structure is now much more elaborate, but it's the only path forward I'm currently able to come up in order to disentangle the existing implementation mess... |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||
| Workflow_Verwijlen.mm | ||