public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Jim Carter <jimc@math.ucla.edu>
Cc: David Sainty <david.sainty@dtsp.co.nz>,
	Mario_Limonciello@Dell.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Make bluetooth-properties fit on smaller displays
Date: Wed, 01 Oct 2008 17:33:00 +0100	[thread overview]
Message-ID: <1222878780.3311.226.camel@cookie.hadess.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0810010904570.18937@simba.math.ucla.edu>

On Wed, 2008-10-01 at 09:26 -0700, Jim Carter wrote:
> On Wed, 1 Oct 2008, David Sainty wrote:
> 
> > xdpyinfo says the DPI is 100x101... heh...
> > 
> >  dimensions:    800x480 pixels (203x121 millimeters)
> >  resolution:    100x101 dots per inch
> > 
> > In reality it's around 133dpi (153mm x 92mm).
> 
> I'm sure the erratic sizing comes from nonuniform font selection.
<snip>

What does all that have to do with the discussion at hand?

> I wonder if the Bluetooth applet follows this rule?  Judging from the 
> discussion, most likely it does, and it's then at the mercy of the distro's 
> setup.

There's resolution independence patches ready to be merged into GTK+.
See:
http://bugzilla.gnome.org/show_bug.cgi?id=546711

> Judging the screenshots that were shown, I think the landscape layout (new) 
> is more practical for the N810.

The N810 doesn't use bluez-gnome.

>   However, the smallest screen I have to 
> deal with at work is the Palm Treo 650 at 320x320px.

Which doesn't run Linux, or bluez-gnome, does it?

>   It wouldn't be 
> running Linux, but if it were, both orientations would be equally bad.  I 
> suspect that handheld devices are the most likely to have Bluetooth 
> accessories, since they have the most limitation in power and USB ports, so 
> special effort should be put in to fit any dialog boxes reliably on the 
> small screens, assuming the distro provides defaults that make this 
> possible.

Please don't go off on tangents. There's a pretty clear discussion
happening, I don't think we want to hear ramblings about other devices
that don't even use bluez-gnome.


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 17:44 [PATCH] Make bluetooth-properties fit on smaller displays Mario_Limonciello
2008-09-29  9:07 ` Marcel Holtmann
2008-09-29  9:15   ` Bastien Nocera
2008-09-29 15:05     ` Mario_Limonciello
2008-09-29 15:22       ` Bastien Nocera
2008-09-29 16:47         ` Emmet Hikory
2008-09-29 23:41         ` Marcel Holtmann
2008-09-30  8:00         ` David Sainty
2008-09-30  8:17           ` Marcel Holtmann
2008-09-30  8:56             ` David Sainty
2008-09-30 13:38               ` Mario_Limonciello
2008-09-30 22:14                 ` David Sainty
2008-10-01 16:26                   ` Jim Carter
2008-10-01 16:33                     ` Bastien Nocera [this message]

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=1222878780.3311.226.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=Mario_Limonciello@Dell.com \
    --cc=david.sainty@dtsp.co.nz \
    --cc=jimc@math.ucla.edu \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox