Re: [Flightgear-devel] GUI options (Was: Aircraft center)

[Torsten D. <to...@t3...>]

>
> I guess I don't see the 'duplicating' - from where I stand, you're
> building a Ferrari, we're rigging together a motorcycle. Your aim is to
> make use of a large set of options, allows 'out of window' rendering, is
> visually more appealing than what we have right now - my aim is to have
> something minimal that 'just works'.
>
As far as I understood, James is working on a way to render dialogs
"in-the-window" within OSG.
And I have no doubt that they will "just work" by punching in some kind of
high-level UI language, probably even our old-style XML will work. Looking
at the huge amount of code James has contributed, it's quality and his
expertise in that area, I am absolutely sure that Qt will be an excellent
choice for the UI.

>
> I honestly can't see the competition here - I see two approaches with a
> rather different focus complementing each other. I'm sorry if that
> de-motivates you, that sure is not the intention.
>
As they both serve the same purpose it is a competition.

>
>  Also - what's
> the idea with Phi for aircraft access? A separate set of special dialogs
> aircraft-side? It's basically the same challenge.
>
I once tried to render the xml dialogs in Phi. I dropped the idea as I
quickly found out that they looked damn ugly and in most cases made no
sense in the minimalistic way they are working.

>
> Well, no - that's the whole point of this discussion - we have a demo up
> and running which can be refined and extended within days/weeks. I guess
> (no promises) if we really wanted and would focus efforts, PUI could go by
> the next release and we'd have a rough replacement.
>
Now, that is an intersting statement. If that is true, probably nobody
objects agains removing PUI and replace it by CUI, keeping the old syntax.
At least for a while. Dropping PUI would be a huge step forward.
I am just a little uncertain who you mean by "_we_ focus efforts". I would
not want to focus on it,  fix related bugs or review merge requests. My
clear focus is on Phi and Qt.
However, I not objecting against the CUI as long as It stays out of the way
if not enabled (or explicitely disabled).

Torsten