All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Florian Boor <florian.boor@kernelconcepts.de>
Cc: openembedded-devel@lists.openembedded.org,
	angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] [RFC] Smallscreen mod for GtkFileChooser
Date: Thu, 10 Jan 2008 18:51:02 +0200	[thread overview]
Message-ID: <6810017939.20080110185102@gmail.com> (raw)
In-Reply-To: <47860F56.7050205@kernelconcepts.de>

Hello Florian,

Thursday, January 10, 2008, 2:28:06 PM, you wrote:

> Hi,

> Joaquim Duran schrieb:
>> Is it possible only apply the patch if GUI_MACHINE_CLASS = "smallscreen"
>> is set?

   Note that the patch is helpful for "bigscreen" devices in OE too
;-).

> in theory yes, but that makes your GTK package specific for each device.

  Yes, and that's bad. But we don't *have to* apply it selectively. As
I tried to describe it in blog, and elaborated in the other mail, I
deliberately made as little as possible appearance and behavior
changes to the dialog. If you'll run it on large screen, the only
change you will notice is that it has a smaller gaps and margins. It
is fully usable otherwise.

  Maybe even that could be elaborated, but note that we apply many
"worse" patches to gtk+ in OE already. Consider disable-tooltips.patch.
It cuts off tooltips unconditionally. Run with mouse? Sorry. Not that
current Angstrom's xserver-kdrive setup allows to run with mouse at
all... etc, etc. No worries, all those issues are on my todo list. And
the sooner we finish with the current issue, the sooner I'll be able
to get to them.

> It
> would be better if the screen size is checked at runtime.

  So, that's what my patch does.

> Ideally GTK would do
> this once and adjust spacing definitions that can be used by GTK implementation
> and applications.

  And here where caveat comes - think about screen rotation. Think
about changing resolutions. Think about these actions happening while
dialog is on screen...

> libgpewidget does it in this way too.

> Greetings

> Florian




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




  parent reply	other threads:[~2008-01-10 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 21:56 [RFC] Smallscreen mod for GtkFileChooser Paul Sokolovsky
2008-01-07 16:51 ` Florian Boor
2008-01-08 14:34   ` Paul Sokolovsky
2008-01-08 16:49     ` Richard Purdie
2008-01-10  9:19       ` Paul Sokolovsky
2008-01-10 10:30         ` Richard Purdie
2008-01-10 16:41           ` Paul Sokolovsky
2008-01-10 10:47         ` [Angstrom-devel] " Florian Boor
2008-01-10 12:31           ` Joaquim Duran
2008-01-10 12:28             ` Florian Boor
2008-01-10 14:35               ` Joaquim Duran
2008-01-11  8:16                 ` problem when i compile image ohviey1
2008-01-11  8:50                   ` pHilipp Zabel
2008-01-10 16:51               ` Paul Sokolovsky [this message]
2008-01-10 17:11                 ` [Angstrom-devel] [RFC] Smallscreen mod for GtkFileChooser Florian Boor
2008-01-10 17:30                   ` Paul Sokolovsky
2008-01-10 11:08         ` Michael 'Mickey' Lauer
2008-01-11 22:45           ` [Angstrom-devel] " Paul Sokolovsky

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=6810017939.20080110185102@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=florian.boor@kernelconcepts.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.