4 ms·

Interesting; do you know which distros do that? I know Nokia started the Qt stuff (for Maemo), but wasn't aware that anybody was continuing to maintain it. But

by mook 9y ago

Interesting; do you know which distros do that? I know Nokia started the Qt stuff (for Maemo), but wasn't aware that anybody was continuing to maintain it. But I haven't looked at things at a level that would have let me know in quite a while.

shmerl 9y ago
SailfishOS developers were dragging it along, but after Mozilla dropped support for IPC Embedlite[1] (they never even accepted it officially), I think they got stuck with outdated Gecko. No idea what they are doing about it. 1. https://wiki.mozilla.org/Embedding/IPCLiteAPI https://wiki.mozilla.org/Embedding/IPCLiteAPI
kuschku 9y ago
The SUSE distros are patching Firefox to use QT dialogs for everything, but kept the GTK core loop.
- shmerl 9y ago
  Why didn't they replace all GTK with Qt and proposed to upstream it? That would have been really good.
  - kuschku 9y ago
    That was done several times before, but Mozilla rejected such proposals. Even if that means Firefox breaks every few weeks due to a new GTK release. Even if that means Firefox never will properly support multi-monitor HiDPI on Linux (and not at all on X11).
    - shmerl 9y ago
      Did they provide any reason, or those who make decisions there have some irrational bias and prefer GTK? I can see why it can be harder to bind to Qt from Rust, but this is now a solved problem I think: https://phabricator.kde.org/source/rust-qt-binding-generator/ https://phabricator.kde.org/source/rust-qt-binding-generator...