4 ms·
> Uses native widgets; > Uses windowless controls on Windows; Don't these contradict each other? What do you mean under "windowless" and why it is important?
by zerr 9y ago
> Uses native widgets;
> Uses windowless controls on Windows;
Don't these contradict each other? What do you mean under "windowless" and why it is important?
Btw, you can list particular advantages/comparison at least over top 3 popular C++ cross-platform UI toolkits: Qt, wxWidgets, Gtk+/Gtkmm.
- mwcampbell 9y agoThose two statements do contradict each other. According to my own quick analysis, this library uses truly native controls on Mac and GTK+, but its own windowless implementations on Windows. The Windows control implementations use uxtheme so they look more or less native, but that's not "native controls" as far as I'm concerned.
- zerr 9y agoInteresting, what advantages this gives, maybe better skinning/theming support? But that doesn't seem to be the main goal of this framework...
- mwcampbell 9y agoIf better skinning is the intended advantage, then it's apparently not implemented yet. I would also like to know the developer's reasoning, since using non-native controls makes it much harder to support accessibility, and this library hasn't yet addressed that.
- maxxxxx 9y agoI think it's easier to port your own drawing code from platform to platform. That's probably why Firefox and Chrome can be multi platform because their rendering code is the same. Doing a cross platform UI library that uses native controls seems a lot of work.
- zerr 9y agoBtw, wxWidgets uses native controls for each platform. You can even get to underlying native control and use platform specific APIs.