Linux bluetooth development
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] More thoughts on bluez-gnome
Date: Mon, 05 Mar 2007 16:46:17 +0000	[thread overview]
Message-ID: <1173113177.23027.34.camel@bnocera.surrey.redhat.com> (raw)

Heya,

I was taking a look at the bluez-gnome source code on Friday, and this
week-end, as well as the interface in general.

I wanted to know what the target use of the bluetooth-applet (and
-properties) was.

The sort of thing that I'd like to see in a GNOME bluetooth applet:
- remove class of device drop-down menus (made a GConf-only option if
really necessary).
- add some integration into HAL (Software on/off, state restoration
after sleep)
- always display the bluetooth icon if a bluetooth device is present,
grayed out if the device is disabled (see above), removed if no adapter
is present at all
- more integration into existing GNOME software (gnome-vfs2-obexftp to
browse phones with Nautilus, gnome-obex-send and gnome-obex-server to
send and receive files).

The applet and the properties windows could also use a lot of cleanup,
codewise, to follow the GNOME style a bit more closely (separate the
auth/passkey code, make the "applet" into an object, use Glade when
possible to generate the interface).

Finally, I'd like to see convenience dialogues (as currently badly
implemented in gnome-bluetooth) for selecting particular Bluetooth
devices. Something aking to MacOS X' Bluetooth UI classes:
http://developer.apple.com/documentation/DeviceDrivers/Reference/IOBluetoothUI/index.html
and
http://developer.apple.com/documentation/DeviceDrivers/Conceptual/Bluetooth/BT_Bluetooth_On_MOSX/chapter_3_section_7.html#//apple_ref/doc/uid/TP30000997-CH215-TPXREF110

If the plan of bluez-gnome is to cater for the advanced Bluetooth
user[1], or the users of desktops other than GNOME, then I think I'll
move my focus onto bringing functionality to gnome-bluetooth instead.

Otherwise, I'd kindly request a CVS account so that my trivial cleanups
can get in faster.

Cheers

[1]: who wants to enable his bluetooth adapters as routers, need to be
able to enable/disable notification area icons, or change device
classes, etc.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2007-03-05 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 16:46 Bastien Nocera [this message]
2007-03-05 20:19 ` [Bluez-devel] More thoughts on bluez-gnome Marcel Holtmann
2007-03-07  0:58   ` Bastien Nocera
2007-03-07 12:00     ` 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=1173113177.23027.34.camel@bnocera.surrey.redhat.com \
    --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