The intention is to switch from the itertools-based filter to the filter available in the TreeExplorer framework. Thus "basically" we just need to copy the solution over, since both are conceptually equivalent. However...... :-( The TreeExplorer framework is designed to be way more generic and accepts basically everything as argument and tries to adapt apropriately. This means we have to use a lot of intricate boilerplate code, just to get the same effect that was possible in Itertools with a simple and elegant in-place lambda assignment |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||