20,741
edits
m (→Announcement) |
(→Canvas) |
||
Line 182: | Line 182: | ||
=== Canvas === | === Canvas === | ||
{{Note|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 (via [[HLA]]) [http://sourceforge.net/p/flightgear/mailman/message/34196458/]. | {{Note|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 (via [[HLA]]) [http://sourceforge.net/p/flightgear/mailman/message/34196458/]. | ||
}} | |||
{{FGCquote | |||
|1= Canvas works fine in this scenario, we can embed the texture or image a Canvas produces into a QtQuick dialog just fine. (It would be possible to reimplement Canvas using Qt but I don’t see any benefit there - the non-Qt builds still need Canvas support for flight-displays and the like) | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34532040/ | |||
| title = <nowiki>[Flightgear-devel] GUI questions (again)</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Oct 11th, 2015 | |||
| added = Oct 11th, 2015 | |||
| script_version = 0.23 | |||
}} | |||
}} | }} | ||