... porting existing PUI dialogs may be considered somewhat boring. True, but it also doesn't take that long and would be worth it. The issue with PUI2Canvas is it misses things and the dialogs look kind of horrible if I do dare say so. I really dislike that "Ubuntu" theme, I think the ...

... http://wiki.flightgear.org/images/9/91/About-dialog-rendered-by-canvas.png http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png

... those having to be edited, all using ~600 lines of code (written during a few weekends): http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png So, not sure where you are seeing the "failure" here - you may in fact be in for a huge surprise here. What you've been describing ...

... into issues supporting pui dialogs via Phi due to nasal, i ended up using the same method to dynamically translate a subset of pui/xml to canvas (pui2canvas), you can still find the corresponding code on the wiki, and it can probably reused as is, or at least easily adapted. If you're going to ...

... (especially in the UI department) - and a number of such efforts have been actively killed off by senior contributors, which is why the whole pui2canvas module has been turned into a tutorial rather than an actual option: Subject: nav.dat update? But FG is pretty good in 'pie in the sky' efforts ...

... dialog file: http://wiki.flightgear.org/Howto:Processing_legacy_PUI_dialogs_using_Canvas http://wiki.flightgear.org/images/0/05/Map-canvas-via-pui2canvas.png The same approach would also work for other features making use of legacy OpenGL code to use the Canvas instead (including the osgText ...

... to get rid of the legacy 2D panels code, at the mere cost of writing a parser to interpret/map 2D panels to canvas gauges (analogous to how pui2canvas works). Once we encourage an element-based extension mechanism, where new drawing primitives can be prototyped/implemented and registered ...

... 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 ...