public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-gnome ui
Date: Wed, 16 Jan 2008 19:14:50 +0000	[thread overview]
Message-ID: <1200510890.26259.52.camel@cookie.hadess.net> (raw)
In-Reply-To: <1200510167.17973.2.camel@teponkone>


On Wed, 2008-01-16 at 21:02 +0200, Teppo Turtiainen wrote:
> Hi guys,
> 
> Let me start by saying that I'm a big fan of Bluetooth (6 devices and
> counting) and of the work you are doing.
> 
> I am not a user interface designer, but I think that the current UI for
> bluez-gnome is pretty awful: There is a Services tab that only geeks
> will understand (what actually is a Serial service?), there are buttons
> that appear/disapper and change contents depending on which bonded
> device is selected, there are non-obvious icons (what does that lock
> next to my phone mean? Is my phone locked?), there is no way to initiate
> pairing with a new device, for some reason it is necessary to ask the
> user for the class of the device when HAL already knows that, etc. I
> tried filing bugs for some of the individual issues, but those got
> wontfixed, so I thought I'd email the list directly. 

I marked it as WONTFIX, because I'm not the maintainer. I think the UI
is pretty rubbish as well, but it works, which is more than can be said
of the previous attempts...

> I think the current crappiness is even more evident when compared to the
> brilliant design for BluetoothManager that was up at live.gnome.org. [1]
> Is there any chance of working towards the more non-geek-friendly vision
> presented on that old BluetoothManager page?

Well, I did that original mockup, so I think it's good as well ;)

> [1] http://live.gnome.org/BluetoothManager?action=recall&rev=16

Cheers


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-01-16 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 19:02 [Bluez-devel] bluez-gnome ui Teppo Turtiainen
2008-01-16 19:14 ` Bastien Nocera [this message]
2008-01-16 19:33 ` Marcel Holtmann

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=1200510890.26259.52.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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