Re: [Flightgear-devel] KBOS runway list? are there 10 or are there 12?

[James T. <jam...@kd...>]

> On 28 May 2017, at 11:56, Stuart Buchanan <stu...@gm...> wrote:
> 
> I could probably re-write the dialog to regenerate itself with the
> correct number of
> rows, as an alternative to the PUI textbox.
> 
> Alternatively, perhaps it's time to retire that dialog in favour of a
> Canvas-based
> approach or something else.
> 
> James - without wanting to open a huge can of worms, what is your current
> think on the in-sim UI and Qt?
> 
> Would it be worthwhile to implement a new version of this dialog in Qt as
> an alternative to the PUI version, perhaps using some of the launcher code?

I would say do the PUI fix for now, I am still very much undecided about which technology to use for in-sim GUI. I am somewhat inclined towards using the Canvas, because it avoids some rendering issues (but exposes a few more, + some performance ones) but the problem is I am fairly unhappy with the GUI / widget API in the Canvas right now - it does not satisfy my ideas about how simple + robust such an API should be. I need to evaluate if the current API can be improved or needs to be drastically changed.

The other issue is to use QtQuick rendered into OpenGL, which has a very nice robust and well-designed API, but adds some dependencies and complicates the rendering architecture, which makes me nervous about multi-window setups and other more esoteric OSG configs.

So, yes, I’d say do PUI for now, since this is worth a fairly quick fix as it’s the default airport.

Kind regards,
James