Hint : It's neither a gfx-driver nor a GUI-toolkit.
Actually it is "just" a filemanager/program-launcher sitting far ontop of these 2....
The initial AMP system would be just as limited as PowerUP was back then, read AMP task would have no direct access to ABox-functions (except for those specially added for comminication).
Once that is working, one might consider rewriting CGX and other drivers for "QBox" and have ABox-apps access it through some virtual drivers (or the other way round, but IMO a 100% "QBox"-MorphOS should be the endgame).
On top of that one might port MUI (which would run alongside ABox-MUI) and eventually Ambient (which than wouldn't have any need for direct ABox-access).
