First, I've looked and it appears that display-x returns the 
physical size of the screen, supposing the server has been 
correctly configured.  I wrote a couple lines tonight that 
should do that on fbdev, supposing the fbdev drivers _can_
be configured and also that they actually/correctly implement
the var_screeninfo.height,width feature.  I'll test it and if
it looks functional, commit it.

This much is sure though -- some targets just do not know
their physical size, which brings us to Stefan's idea of allowing
it to be configured in a file.  Doing so just for that purpose
of course would be overkill -- envoronment variables would be
an easier way, but that did get me thinking....

What if, libggi.conf were to look something like this:

display-x       display/X.so            DEFMODE=640x480;DISPLAY=-nocursor
display-xlib    display/Xlib.so         DISPLAY=-nocursor
display-fbdev   display/fbdev.so        DEFMODE=600x800

The options would be overridden by the environment, but would be there
if the environment variables were not set...

This could also be expanded to allow sysadmins to define their own "displays":

display-xfullscreen   display/X.so      DEFMODE=320x200;DISPLAY=-inroot

Comments?

P.S. _requesting_ certain physical dimensions be used (by increasing the
size of the unused border or to size the xwin) will have to wait until 
after release; it will take a good days work to do all the targets correctly.

--
Brian

Reply via email to