Originally posted by johnc
View Post
Announcement
Collapse
No announcement yet.
The GTK3 Port Of Firefox Is Making Progress, Firefox Can Run On Wayland
Collapse
X
-
-
Originally posted by johnc View PostHowever, I also see the window bar as being used for managing the window, and not being a place to cram all kinds of garbage shit from the app in there because somewhere along the line somebody got "inspired" and decided that menu bars and tool bars are "dated" concepts. So now we have 300px tall title bars with hidden menus and ugly icons. Big problem solved there.
These 'modern' GNOME apps that replace the thin titlebar with another big-ass toolbar (that I don't use, because there are keyboard shortcuts for things I do frequently and menus for things that I don't) and take away the window manager's/my ability to move the window whereever it wants without the application's consent (window management is the window manager's, not the application's responsibility) as well as the ability to have consistent title bar styling (My XFCE desktop has dark title-, menu- and task bars, which is respected by all GTK2 apps, all Qt apps, most older GTK3 apps and apps like Firefox, but gedit, evince et al. decided "hey, the user definitely wants a huge white title bar, let's do that!". That's the point when I stopped using them.).
I'm glad Kwin still wants to draw decorations itself under wayland, and that's why I'm waiting for that before trying to build a WL desktop.
Or does Enlightenment do the same?
Anyway, none of these have full wayland modes present in my distro (Arch)'s packages AFAIK. (Correct me if I'm wrong)
Comment
-
Originally posted by emblemparade View PostYou also make the odd conclusion that "The very fact that so many projects are switching, and the switch is pretty much entirely one-directional, should tell you that there is something different." Corellation doesn't equal causation.
I was hoping to see some reaction from the GTK/Gnome side about whether they consider the criticism raised to be valid or not and whether they do want to improve the situation. So far I am out of luck.
That *some* projects are switching can say many things, but that doesn't lead to the conclusion that Qt is generally better than Gtk+ and that all projects should switch.
The reason can be very project-specific reason, for example the choice of programming language (C or C++), or licensing ideology.
It could also be jumping on the bandwagon. Trends are funny: in 5 years, there might be something really annoying happening with Qt (too much focus on mobile or something) and then "so many projects" will want to switch back. We've seen these changing fashions a lot.
Comment
-
Originally posted by psychoticmeow View PostDo you really want to go back to the days where the theme engine had final say over what it was possible for designers to implement?
Comment
-
Originally posted by smitty3268 View PostRead the article - they've added the ability to have the main Firefox process run GTK3 while the plugins can still link to GTK2 in their own process.
Cheers,
_
Comment
-
Originally posted by anda_skoa View PostI was surprised to read about this bit. I had assumed that like any other browser out there they had been running plugins out-of-process for ages already.
Comment
-
Originally posted by anda_skoa View PostI was surprised to read about this bit. I had assumed that like any other browser out there they had been running plugins out-of-process for ages already.
The obvious approach is of course to add a new library called libmozgtk that provides the symbols for *both* GTK2 and GTK3 and have two implementations of that library, one using GTK3 and leaving the GTK2-only symbols blank and the other using GTK2 and leaving the GTK3 symbols blank. The idea apparently is that the UI process will use the GTK3-flavor and never access any of the GTK2 symbols (which will cause a core dump) while the plugins are using the GTK2-flavor and will never use GTK3 (which would again cause a core dump).
Now let's wait for the first plugin to use GTK3 and watch this whole thing blow up.
Never mind the maintenance overhead of keeping the two flavors of libmozgtk in sync with GTK3 (and GTK2, but that is rather stable by now).
Comment
-
Originally posted by wargames View PostExactly. Too bad Eclipse has moved to GTK3. I should try Intellij IDEA...
Oh, and let's not forget GIMP is also moving to GTK3. Probably in 2018 though
Comment
-
Originally posted by Gusar View PostThey have. Since Firefox 3.6. What's a recent addition is the ability to use GTK2 plugins in a GTK3 Firefox, changes to the plugin container and IPC with Firefox were required for that.
Didn't know Firefox had application plugins as well, I only knew about extensions
Cheers,
_
Comment
Comment