Ichthyostega
723d1e0164
so yes, it is complicated, and inevitably involves three layers of indirection. The alternative seems to bind the GUI direcly to the Session interface -- is there a middle gound? For the messages from GUI to Proc, we have our commands, based on PlacementRef entities. But for feeding model updates to the GUI, whatever I consider, I end up either with diff messages or an synchronised access to Session attributes, which ties the responsiveness of the GUI to the Builder operation. |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| renderengine.html | ||
| uml | ||
| workflow.mm | ||