@Hooray: The mammoth task of GC is that GC is highly solution dependent. What works well for one piece of software might be terrible for another. So for Nasal embedded in fgfs, you would probably need to compare different techniques ...

... but rather pure opinions. I will stick with my opinion that Thorsten's desire to have a pure CUI driving FG - which does not match your aim - is a mammoth task. Anyway, please feel free to correct any of my following opinions and views: ⋅  The PLIB GUI (PUI) is dead and it will be stripped ...

... to strip out PUI from the compilation and provide a full CUI interface that provides 100% of the functionality of the current PUI! I say it's a mammoth task, so I'm hoping you can prove me wrong ;) @Thorsten - one of the ideas of using Qt5 is to provide dialogs that the current primitive PUI ...

... menus ? The entire context of my posts is that the PUI -> QUI transition is occurring, because a PUI -> CUI transition is not planned, would be a mammoth task, and there is no one working on that transition. There is nothing in there about the current CUI efforts. Due to the responses here, I ...

... etc. And it will have to be packaged as one toolkit. The dumping of the XML menu system will also be a big issue (see below). This will be a mammoth task, by anyone's measure. That is why almost everyone just uses one of the pre-built toolkits, rather than spinning their own. So I see this ...