On Wed, Mar 30, 2011 at 10:51 PM, Manu Gupta <manugupt1@gmail.com> wrote:

Hi All

SaX3 is a GSoC 2011 project. I have applied for it. So in order to strengthen my proposal I need some help from you guys. So if you can help me.

Excellent idea! One of my most common usages for sax2 was something like "sax2 -r -m 0=fbdev" whenever I'd bork fglrx. A few releases ago, when I had a radeon 200m, the radeon module didn't work at all, so it used to be a hair simpler to use sax to switch modules for me. Making sax3 as much cli-oriented as well as the sax3 gui would help. On Thu, Mar 31, 2011 at 11:00 AM, Christian Boltz <opensuse@cboltz.de> wrote:

And in general: SaX should write out only the config parts that are needed/wanted by the user, not a complete xorg.conf. So if someone only changes the keyboard layout, SaX should only generate a configuration sniplet for the keyboard.

Agreed, however I think sax3 should use the xorg.conf.d, splitting the sections up in to files, and not making one big nasty xorg.conf like sax2 did. As crazy as the question might sound, would it be possible to merge xrandr with sax3? So for example, if the user asks for a change that can be done with KMS, to do the change immediately (if the user agrees) and/or to write it to the xorg.conf.d at the same time? That way there'd be just one central place to go to for playing around with monitors? Accompanying sax3, there'd be a yast-sax3 module, right (this would benefit new users, primarly), and it would be re-integrated in to the non-automatic configuration during the installation process? Zack Buhman -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org