4 ms·
Presumably GTK is not just used from drawing visible elements but also for things like file pickers, print windows etc.
by robin_reala 9y ago
Presumably GTK is not just used from drawing visible elements but also for things like file pickers, print windows etc.
- kuschku 9y agoWhich sucks so horribly that several distros actually maintain a full fork of Firefox where all those are patched to use Qt instead.
- mook 9y agoInteresting; 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 agoSailfishOS 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 agoThe SUSE distros are patching Firefox to use QT dialogs for everything, but kept the GTK core loop.
- shmerl 9y agoWhy didn't they replace all GTK with Qt and proposed to upstream it? That would have been really good.
- kuschku 9y agoThat 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 agoDid 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...
- shmerl 9y agoFennec used to work without GTK? And Firefox on Android does, but there it's probably using another toolkit. It causes this exact problem - porting Firefox to a new system is impossible without rewriting all that.
- Sylos 9y agoYeah, Android Firefox uses the native Android UI toolkit. A long time ago, they had it in XUL, which allowed for some really nice customization and just in general a more conform behaviour with the desktop browser, but performance back then was really just terrible, so that's why they changed it to the native Android UI toolkit.