ajs, on Mar 2 2007, 07:48 PM, said:
Firefox, on the other hand, used to have a Qt port, but it's mostly been abandoned. Shame on Firefox.
Regardless, it can still use other toolkits.
http://developer.moz...raphics_Toolkit:
ac_add_options --enable-default-toolkit=gtk2|gtk|xlib|qt|cairo-gtk2|cairo-xlib|cairo-windows|windows|mac|cocoa|cairo-cocoa|os2|beos|photon
Selects the graphics toolkit. This is not needed for Windows/OS2/BeOS/Photon, since these platforms automatically select the correct toolkit. It is also not needed on Mac, unless you are building Camino on an older branch (Camino uses --enable-default-toolkit=cocoa).
On *nix platforms, selects the graphics toolkit to use. GTK2 and GTK are both well-tested. xlib is considered a tier-3 platform. Qt and cairo are experimental, you will find bugs. On trunk, use cairo-gtk2 (the default).
Really, it's worth a shot, if anything just to play around with it a bit and experiment.
I personally don't have any problems with the standard GTK2 configuration that Portage builds. The file selector isn't that big of a deal to me since you really don't use it *that* much in web browsers, and I've pretty much given up on seeing true UI consistency in *any* platform.