Re: Very Late Progress Report - RandR

["Pascal Schoenhardt" <stoanhart gmail com>]

Hi everyone,

Good to see this mentioned.

This is something I probably should have discussed earlier. What about
users who do not support randr 1.2? I have always assumed this tool
would replace the Screen Resolution capplet that is in place now.
However, if so, it must be backwards compatible, and still be able to
set xorg.conf stuff. If this is beyond the scope of this project, let
me know! I would be happy to drop that bit - less stuff to do!

On 7/20/07, Pascal Schoenhardt <stoanhart gmail com> wrote:
> Hi everyone,
>
> Good to see this mentioned.
>
> This is something I probably should have discussed earlier. What about
> users who do not support randr 1.2? I have always assumed this tool
> would replace the Screen Resolution capplet that is in place now.
> However, if so, it must be backwards compatible, and still be able to
> set xorg.conf stuff. If this is beyond the scope of this project, let
> me know! I would be happy to drop that bit - less stuff to do!
>
> Pascal
>
> On 7/19/07, Nicolas Trangez <eikke eikke com> wrote:
> > On Thu, 2007-07-19 at 11:07 +0200, Vincent Untz wrote:
> > > Hi Pascal,
> > >
> > > Le jeudi 12 juillet 2007, à 11:25 +0100, Pascal Schoenhardt a écrit :
> > > > The "engine" will be the majority of the code. It will be responsible
> > > > for the storing, loading, and managing user profiles in GConf, and for
> > > > interfacing with the Xrandr library directly to apply changes. It will
> > > > also be responsible for writing changes to the xorg.conf file, when
> > > > necessary.
> > >
> > > Is it really needed to write to xorg.conf? It'd be better to avoid doing
> > > something requiring some privileges.
> > Indeed, what's the use case of this? Should be perfectly possible to
> > store the randr settings to apply in gconf and send the randr requests
> > to the server when appropriate (just like done to set input device
> > properties, which is why you can get a warning dialog when your GNOME
> > keymap setting differs from the one your server uses (the one stored in
> > xorg.conf)).
> > afaik xrandr is about *not* storing information in xorg.conf, but
> > discover it at runtime...
> >
> > Nicolas
> >
> >