20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 13:55, 24 February 2017
, 24 February 2017no edit summary
mNo edit summary |
No edit summary |
||
| Line 52: | Line 52: | ||
While most people seem to agree PUI needs to be replaced, it sounds as if the fallout from doing [using Qt5] so would be more painful (cumulatively) than the pain its existence causes.<ref>{{cite web | While most people seem to agree PUI needs to be replaced, it sounds as if the fallout from doing [using Qt5] so would be more painful (cumulatively) than the pain its existence causes.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35623408/ | |||
|title = <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jan 24th, 2017 | |||
|added = Jan 24th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Obviously, it’s most important that people feel able to use and contribute to the project, far more so that whether a particular feature gets implemented or not.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35623408/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35623408/ | ||
|title = <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki> | |title = <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki> | ||