... the same 10 hours spent by someone working on the Qt5/QQ2 port would provide more bang for the buck, and obviously 10 hrs spent fine-tuning the pui2canvas parser, would provide a fast track solution to get rid of PUI without having to be a core developer, and even without having to touch any ...

... http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png Background: http://wiki.flightgear.org/PUI http://wiki.flightgear.org/Unifying_the_2D_rendering_backend_via_canvas http://wiki.flightgear.org/Canvas_Widget_Matrix ...

... http://wiki.flightgear.org/images/9/99/Logging-dialog-via-pui2canvas.png http://wiki.flightgear.org/images/2/23/View-dialog-comparison-pui2canvas.png In other words, all the building blocks for a PUI-free in-sim ...

... are registered as fgcommands, at that point the UI stack becomes totally relevant - because you'd be using primarily XML and fgcommands again. The pui2canvas parser can help accomplish that, and therefore it could even facilitate migrating to a different UI back-end, which may involve both, Qt ...

... equivalent: http://wiki.flightgear.org/Howto:Processing_legacy_PUI_dialogs_using_Canvas http://wiki.flightgear.org/images/6/66/Scenarios-via-pui2canvas.xml.png Note that this indeed done procedurally, i.e. at runtime - the original PUI/XML dialog wasn't touched to create the Canvas equivalent. ...

Octal450 wrote in Tue Oct 01, 2019 9:57 pm:You realize, johan, that dialog is PUI not canvas...

it can be if it goes through the PUI2Canvas convertor

... - which is why making things work in a standalone setup requires some familiarity with fgfs/nasal internals, I ran into that when I prototyped the pui2canvas parser, which also needed a way to deal with Nasal blobs embedded in XML files, but also with procedurally created dialogs. It would be best ...

... based parser to see how feasible a Canvas based PUI replacement would be (proof-of-concept, i.e. under 500 LOC): http://wiki.flightgear.org/Pui2canvas http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png Later on, the only core developer intimately familiar with the process ...

... http://wiki.flightgear.org/Qt5_Launcher http://wiki.flightgear.org/QtQuick_use_in_FlightGear http://wiki.flightgear.org/Pui2canvas Besides, while re-implementing a working Nasal VM would of course be possible, that would not magically fix up coding issues that crept up ...

... map-canvas.xml): http://wiki.flightgear.org/Howto:Processing_legacy_PUI_dialogs_using_Canvas http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png Notably, the same mechanism could also work for a Canvas-enabled Phi back-end: http://wiki.flightgear.org/Read_canvas_image_by_HTTP http://wiki.flightgear.org/images/thumb/4/45/Canvas-ND-served-via-httpd.png/800px-Canvas-ND-served-via-httpd.png ...

... for some * try up/down grading GPU driver, maybe there's a sweet spot * canvas rather than PUI also solves your thing, there's an experimental pui2canvas module which renders you something for many dialogs, although it ain't pretty

... the opposite took place (just to provide a context around your choice of words and your tossing around of acronyms) : http://wiki.flightgear.org/Pui2canvas https://sourceforge.net/p/flightgear/mailman/message/29584988/ I'm even more convinced now that we should move the 2D panel and HUD rendering ...

... simple parser to load/animate 2D panel instrurments from fgdata - and this could be easily extended for these purposes. I think this was prior to pui2canvas actually - i.e. I used this to bootstrap the pui2canvas stuff. This would have the added advantage, that these instruments are not just textures, ...

... would be much easier to code a simple parser that loads the XML file and maps that to a handful of Canvas primitives, analogous to svg.nas (or the pui2canvas parser). For starters, see: https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.xmlpanel https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.minipanel ...

... as long as those are not using any Nasal blobs, but only fgcommands. Torsten's conclusion is in line with my own experiments relating to the "pui2canvas" parser: if people had realized this much earlier, we could have introduced custom fgcommands for all sorts of different purposes (even ...