PCSX2 Documentation/Measuring the Benefits of wxWidgets: Difference between revisions
PCSX2 Documentation/Measuring the Benefits of wxWidgets (view source)
Revision as of 18:12, 25 June 2024
, Tuesday at 18:12Update.
No edit summary |
(Update.) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<center>{{Warning|<big>'''This guide is outdated as PCSX2 now uses Qt!'''<br/>Please refer to the PCSX2 Discord server if you wish to help with programming.</big>}}</center> | |||
''Originally written by Jake Stine'' | ''Originally written by Jake Stine'' | ||
| Line 32: | Line 33: | ||
In all the wxWidgets experience so far has been a decent one. There are a few annoyances, but those tend to be more the fault of cross-platform considerations (some things are not supported well under Linux, or vice versa), or more commonly due to limitations and design flaws in the C++ language itself rather than of wxWidgets (in particular, C/C++ make it especially difficult to work with unicode strings in a 'nice' way). For the most part wx tries to model itself in the image of the .NET Framework and Java Framework API designs, which are good designs to follow. | In all the wxWidgets experience so far has been a decent one. There are a few annoyances, but those tend to be more the fault of cross-platform considerations (some things are not supported well under Linux, or vice versa), or more commonly due to limitations and design flaws in the C++ language itself rather than of wxWidgets (in particular, C/C++ make it especially difficult to work with unicode strings in a 'nice' way). For the most part wx tries to model itself in the image of the .NET Framework and Java Framework API designs, which are good designs to follow. | ||
{{PCSX2 Main Documentation Navbox}} | |||