From: Durk T. <dur...@gm...> - 2015-06-11 08:31:16
|
Hi Thorsten, I can probably give a quick heads-up: Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. 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. For the record, I believe that I should also mention that Torsten Dreyer, who had just started working on phi, was also present at this meeting and agreed to this approach. For the time being, we see no conflict of interest here, as both of these approaches serve somewhat different purposes. Likewise, building a QT based GUI is not in any way meant to obstruct the further development of a Canvas based GUI. We did voice some concerns as to whether the need to re-implement a complete widget is worth the cost is terms of development effort. The beauty of open source is that there's more than one way to do things, however. Especially in a completely modular environment. Cheers, Durk Renk, Thorsten schreef op 11/06/15 om 07:36: >> Replace the plib GUI with Qt. This will improve the maintainability of >> the GUI as well as being visually more appealing. > Maybe someone can explain a bit on this one. I've seen all sorts of claims (this will make SG functionality obsolete, this adds a huge dependency, this is good, this is bad,...) > > I'm seeing TorstenD's Phi, Clement was working on a canvas GUI, there's Qt on the horizon and I guess that's James' project for the integrated launcher,... I've read TorstenD's comments on multiple co-existing GUIs in the forum. > > So, what is the agreed-upon plan? Have three (the canvas GUI, the Qt GUI and Phi)? > > Do we expect any breakage / bad side effects or will the existing xml definitions of menus be parsed just fine? > > What should I think of expressed worries of 'Qt adding a huge dependence'? > > * Thorsten > ------------------------------------------------------------------------------ > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |