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

... I can entirely relate to the key argument some of you have been making (but certainly NOT in the context of Thorsten's quoted comments) - the pui2canvas effort is a much better example, because it's been actively discouraged on the devel list by some of the most senior/active core developers ...

Real world vehicles will be added once someone has made a simple GPS model with map like this (so that I can attach to every vehicle )

... popup that is populated with a Layout and layout items (widgets). I am not sure what else is really needed/missing - but when I prototyped the pui2canvas parser, I ended up emulating missing widgets by using a combination of existing widgets. For instance, for any of the PUI list widgets, I ...

... inevitably need support for independent map instances - the current PUI/XML approach is rather inflexible here. As a matter of fact, not even the pui2canvas parser I once prototyped can turn such dialogs into multi-instance dialogs, because they contain numerous hard-coded assumptions. Which is ...

... 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 For testing purposes I was using dialogs with lots of dynamic behavior, i.e. embedded Nasal stuff and update semantics implemented on ...

... should be some additional configuration for "base" tile maps. Anyway great work for all contributors ! Like I mentioned previously, the pui2canvas parser is a fairly simple piece of Nasal code that started out being under 300 LOC, meanwhile it is roughly twice that - but due to it being ...

... also be straightforward to provide a UI to add/edit and maintain/update entries. Regarding the PUI/Canvas "unification", there is the pui2canvas parser - but for something like the map-canvas.xml dialog, my suggestion would be to create a new Canvas based dialog file from scratch and ...