2 ms·
> This seems to me to be a far more productive approach that trying to come up with an API that supports only the common subset of features shared between Apple
by chrisseaton 11y ago
> This seems to me to be a far more productive approach that trying to come up with an API that supports only the common subset of features shared between Apple's UI toolkit, Windows UI toolkit, and Linux.
But an API with the common subset of features is the whole philosophical point of wx! If you're going to criticise them for that you might as well criticise screwdrivers for turning screws. That's what they were built for.
- dekhn 11y agoWell, then I disagree with wx's approach. Not only is it more inflexible, the qt solution of creating a styled UI that can be adapted to look native, while being portable and not preventing people from customization, seems to be more flexible. Note also that Wx runs on top of Qt. Why not drop Wx and just use Qt directly?
- mark-r 11y agoWx doesn't run on top of Qt, it simply has an option to use Qt as its back end engine in place of e.g. the Windows native API. You can do a Windows build that doesn't have Qt anywhere in sight.