20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
→Dependencies
m (→Dependencies) |
|||
| Line 59: | Line 59: | ||
If, how and when the internal gui can leverage Qt is under investigation and in such an early state that those responsible preferred to not announce anything yet. If this ever happens, this will be discussed on the mailing list<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref> | If, how and when the internal gui can leverage Qt is under investigation and in such an early state that those responsible preferred to not announce anything yet. If this ever happens, this will be discussed on the mailing list<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref> | ||
{{FGCquote | |||
|There's been a strong devision of opinion among a couple of core developers with respect to the question whether a QT dependency is desirable or not. In one of the hangouts, a couple of months ago, we had the chance to discuss the pros and cons, when the most outspoken developers regarding this issue were both present. We concluded that a QT dependency was undesirable, unless it had a specific benefit. With this in mind, I proposed to consider the option of allowing a QT dependency in only one module (call it FGGui). For all practical purposes, this would be a platform independent replacement of fgrun, but because of the proposed modularity, it will appear to be seamlessly integrated with FlightGear. Both developers representing the opposite ends of the debate could live with this compromise. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/34196458/ | |||
|title=<nowiki>Re: [Flightgear-devel] Policy Document and V4.X Roadmap</nowiki> | |||
|author=<nowiki>Durk Talsma</nowiki> | |||
|date=<nowiki>2015-06-11</nowiki> | |||
}} | |||
}} | |||
=== Canvas === | === Canvas === | ||