On Mar 17, 08 12:03:46 +0100, Rodrigo Moya wrote:
We have now patched gnome-xgl-settings to not contain any configuration at all (it just calls ccsm for all config), so it is now just a simple frontend to gnome-xgl-switch.
O-key. Does it still test the graphics card against the database, i.e. does it verify whether Xgl / AIGLX will be able to run on this card at all?
I've been asking and it seems compiz users in KDE use the same ugly gnome-xgl-settings, so we've been discussing (in #opensuse-factory and -gnome) about having this functionality (calling, or doing what, gnome-xgl-switch does) in YAST. The alternatives being, a) keep gnome-xgl-settings, and b) have a per-desktop solution. For b), in GNOME we would add a 'Desktop effects' tab to the appearance capplet, like Ubuntu does
This is no in our realm, if the KDE and Gnome guys agree on having this in Yast, this would be awesome. OTOH we should be aware that with Yast we do explicitly NOT mean sax2.
Not sure if as a separate module, or just under the Display config in YAST, since it's just one button ("Enable XGL").
Hm. IMHO this requires too much low-level knowledge.
I would consider the best solution to have a switch for "Enable Desktop
Effects", and then some sub-option (with reasonable defaults filled it
depending on the graphics card) to select between a) "Xgl" and
b) "AIGLX / Native Support" (if you want to be perfect about this, write
"Native Support" for nvidia, "AIGLX" for all others). So users who care
about the technical foundation can choose, and for all others it's clear
that this is not important to look upon.
The next question is: should this be a system-wide configuration or a
per-user configuration? If Xgl is selected, this just *has* to be
system-wide, using Xgl without compiz doesn't make any sense at all, and
is typically slower than with using compiz. OTOH with AIGLX/Native this
could be a per-user option.
I don't know how to solve this issue in a way that it is understandable
for a typical not-too-technical user. But as most systems are run as
single-user machines anyway, this is probably a no-brainer, and we
should just go for system-wide settings.
HTH
Matthias
--
Matthias Hopf