Bureaucrats, ninja, Administrators
67,566
edits
PCSX2 Documentation/Measuring the Benefits of wxWidgets: Difference between revisions
PCSX2 Documentation/Measuring the Benefits of wxWidgets (view source)
Revision as of 19:32, 5 April 2015
, 5 April 2015no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DocTabs|Section=2}} | |||
''Originally written by Jake Stine'' | ''Originally written by Jake Stine'' | ||
| Line 33: | Line 34: | ||
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 Documentation Navbox}} | {{PCSX2 Starting Documentation Navbox}} | ||