All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Mon, 9 Jul 2007 16:57:35 +0300	[thread overview]
Message-ID: <161888669.20070709165735@gmail.com> (raw)
In-Reply-To: <1005211919.20070709153513@vanille-media.de>

Hello Dr.,

Monday, July 9, 2007, 4:35:13 PM, you wrote:

[]

> I agree with Paul's "they provide *some default* screen resolution and
> orientation.". Almost all our screen devices can be rotated on-the-fly
> anyway. The MACHINE_DISPLAY_ namespace is mainly UI frameworks and
> applications, as much as native framebuffer rotations and stuff are
> important to know, they're less relevant here.

  Yes, that's why I responded to Koen's discussion of formfactor
package. We won't get around runtime support for multiple resolutions,
rotations, etc. What it will be, is another question for further
consideration.


  As for the machine settings in question, they serve very specific
purpose, and not hardcode that device is bound to be in that
resolution and rotation all the time. To sum up, their purpose is:

1. Provide consistent way to configure packages which require screen
resolution parameter (usecase: fbreader)
2. To not install large-size graphic resources which won't be
needed/used on a specific device "by default", and at the same time,
to install the resource which will fit a device best (again just in
its default config). (usecase: opie-taskbar's background images).

> Regards,

> :M:



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




  parent reply	other threads:[~2007-07-09 14:03 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
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 [this message]
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=161888669.20070709165735@gmail.com \
    --to=pmiscml@gmail.com \
    --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.