All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Graeme Gregory <dp@xora.org.uk>
Cc: "Dr. Michael Lauer" <mickey@vanille-media.de>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Mon, 9 Jul 2007 17:40:03 +0300	[thread overview]
Message-ID: <716172870.20070709174003@gmail.com> (raw)
In-Reply-To: <20070709142544.GF2336@p3n3tr4t0r.internal>

Hello Graeme,

Monday, July 9, 2007, 5:25:44 PM, you wrote:

> On Mon, Jul 09, 2007 at 04:19:25PM +0200, Dr. Michael Lauer wrote:
>> > Maybe a MACHINE_DEFAULT_ROTATION is also needed.
>> 
>> I don't think so. What applications care about is if portrait or
>> landscape is the common default and this is already encoded in HEIGHT
>> and WIDTH.
>> 
> Applications do care, a short snippet of /etc/X11/Xserver

>         "SHARP Shepherd" | "SHARP Husky" | "SHARP Corgi")
>                 ARGS="$ARGS -dpi 200 -rgba rgb" ;;
>         "SHARP Spitz" | "SHARP Akita" | "SHARP Borzoi")
>                 ARGS="$ARGS -dpi 200 -rgba rgb -screen 480x640@270" ;;

> Why restrict yourself to the simple usecase of opie backgrounds when
> the information could be used in far better ways.

  So you see, why I was so enthusiastic about that formfactor thingy,
right? ;-)


> If this information was taken from MACHINE_ variables then a large chunk
> of this case statement could be removed. But the way you want to do it
> the information is in machine.conf, xserver-common somwhere, and a variety
> of other places. And all because you refuse to use real information but
> some pre-parsed info that is narrowly defined for one application.

  That's common problem of community discussions - they become
ontological arguments. And we discussed matter of screen size in
particular and other machine feature in general many times already.
Time to start with something, that's idea here ;-). I strongly believe
that we won't stop there, but go on.

  As for xserver-common, it's pretty simple, not we (OE) maintain it,
but GPE project, and they should be consulted if there're ready to
give away hardware param detection to standalone hardware
detection script. So again, not all can happen immediately, but I
really glad people care about this (because it was pain in the neck
for me all the time).


> Graeme


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-07-09 14:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08  1:11 [RFC] Adding screen dimensions to machine configs Paul Sokolovsky
2007-07-08  7:16 ` Koen Kooi
2007-07-08  8:39   ` Dr. Michael Lauer
2007-07-08  9:26   ` Richard Purdie
2007-07-08 12:00     ` Stanislav Brabec
2007-07-08 14:27       ` Richard Purdie
2007-07-09  0:53   ` Rod Whitby
2007-07-09  5:31     ` Stelios Koroneos
2007-07-09 12:43   ` Paul Sokolovsky
2007-07-09 13:17     ` Graeme Gregory
2007-07-09 13:35       ` Dr. Michael Lauer
2007-07-09 13:42         ` Graeme Gregory
2007-07-09 13:52           ` Dr. Michael Lauer
2007-07-09 14:03             ` Graeme Gregory
2007-07-09 14:19               ` Dr. Michael Lauer
2007-07-09 14:25                 ` Graeme Gregory
2007-07-09 14:40                   ` Paul Sokolovsky [this message]
2007-07-09 15:15                   ` Marcin Juszkiewicz
2007-07-09 20:30                     ` Koen Kooi
2007-07-09 22:03                       ` Richard Purdie
2007-07-09 15:44                 ` Florian Boor
2007-07-09 14:23               ` Marcin Juszkiewicz
2007-07-09 14:25               ` Paul Sokolovsky
2007-07-09 15:11                 ` Marcin Juszkiewicz
2007-07-09 13:57         ` Paul Sokolovsky
2007-07-09 13:41       ` Paul Sokolovsky
2007-07-09 15:55     ` Richard Purdie
2007-07-09 20:01       ` Dr. Michael Lauer
2007-07-09 20:19         ` Graeme Gregory
2007-07-09 20:44           ` Richard Purdie
2007-07-09 20:21         ` Koen Kooi
2007-07-09 21:36           ` Paul Sokolovsky
2007-07-09 21:21         ` Paul Sokolovsky
2007-07-10 10:33           ` Dr. Michael Lauer
2007-07-12 12:36             ` Paul Sokolovsky
2007-07-08 11:36 ` Michael Krelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=716172870.20070709174003@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=dp@xora.org.uk \
    --cc=mickey@vanille-media.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.