public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-gnome ui
Date: Wed, 16 Jan 2008 20:33:38 +0100	[thread overview]
Message-ID: <1200512018.7978.83.camel@aeonflux> (raw)
In-Reply-To: <1200510167.17973.2.camel@teponkone>

Hi Teppo,

> 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. 

to be quite honest it is not that simple. I also never said that this is
a perfect UI, but it is a working one.

With the service tab, I fully agree. It was written from a full
technical background in mind and stuff like that should not be exposed
to the end user. However there are limitations to a certain degree and I
haven't seen any other proposal so far.

For the explanations of the icons. Write a patch that utilizes tooltip
to explain them.

In the class of device case, we actually do use HAL. However I wanna
have a way to not use HAL and set the class by myself. In case the "Use
HAL" checkbox is clicked we could go ahead and hide the class selection.
However that is not as simple as it sounds. You would have to hide the
box for all adapters. Remember this UI supports seamlessly multiple
adapters.

> 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?

The answer to these kind of comments/questions is always the same. Send
in patches that will improve it.

Regards

Marcel



-------------------------------------------------------------------------
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

      parent reply	other threads:[~2008-01-16 19:33 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
2008-01-16 19:33 ` Marcel Holtmann [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=1200512018.7978.83.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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