20,741
edits
mNo edit summary |
|||
Line 143: | Line 143: | ||
}}</ref> | }}</ref> | ||
As of mid 2016, it is pretty safe to say that it's less than a handful of widgets that are now missing to be able to approximate most PUI widgets/dialogs - it goes without saying that this won't look as good as a Qt5 UI, but it also won't have the costs associated with it - i.e. you could say, the pui2canvas approach is merely a simple fasttrack concept to get rid of PUI completely, without having to manually port any of the existing resources necessarily.<ref>{{cite web | As of mid 2016, it is pretty safe to say that it's less than a handful of widgets that are now missing to be able to approximate most PUI widgets/dialogs - it goes without saying that this won't look as good as a Qt5 UI, but it also won't have the costs (amount of work) associated with it - i.e. you could say, the pui2canvas approach is merely a simple fasttrack concept to get rid of PUI completely, without having to manually port any of the existing resources necessarily.<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=289322#p289322 | |url = https://forum.flightgear.org/viewtopic.php?p=289322#p289322 | ||
|title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> | |title = <nowiki> Re: Aircraft Center | pui2canvas parser (devel-list follow-u </nowiki> |