4 ms·
Wikipedia: >On some platforms (such as MeeGo and KDE) Qt is the native API. Some other portable graphical toolkits have made different design decisions; for ex
by heinrich5991 11y ago
Wikipedia:
>On some platforms (such as MeeGo and KDE) Qt is the native API. Some other portable graphical toolkits have made different design decisions; for example, wxWidgets uses the toolkits of the target platform for its implementations.
As far as I know, it's also true that Qt doesn't try to use native widgets, it instead tries to draw them on its own (resulting in more possibilities of course).
- scrollaway 11y agoKDE is not a platform, it's a desktop environment based on Qt that runs on top of X11 (just like LXQt). So that article is misleading.
- coldtea 11y agoBesides maintaining the eponymous desktop environment, KDE is very much a platform, leveraging Qt, but also offering its own core libs and infrastructure for tons of stuff. So much so, in fact, that the title of their webpage is: "KDE - The KDE development platform". I should know, I've been following (and occasionally participating) in the project since 1998.
- scrollaway 11y agoIt is not a platform in the sense that's meant in the post above, which is why I said the article is misleading, not wrong. Like you said, KDE leverages Qt. Qt doesn't leverage KDE in the sense that "Qt's native platform is KDE". When you say "native" when talking about a cross-platform toolkit, you're implying the toolkit was first designed to run on that platform and then ported to others. Qt predates KDE, as you well know. Are we done splitting hairs?
- coldtea 11y ago>When you say "native" when talking about a cross-platform toolkit, you're implying the toolkit was first designed to run on that platform and then ported to others. No, you're just implying (as the parent did) that the platform (KDE) had picked and stuck to the toolkit (Qt) as its basis, unlike Wx which has multiple.