From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Another bluez-gnome patch
Date: Sat, 24 Feb 2007 18:25:27 +0100 [thread overview]
Message-ID: <1172337927.11537.19.camel@violet> (raw)
In-Reply-To: <1172337118.31852.10.camel@cookie.hadess.net>
Hi Bastien,
> > > Here's an updated patch for the bluez-gnome applet and properties:
> > > - Use HAL to determine the device class, if HAL is available
> >
> > I added this part to the CVS now. However we need another GConf setting
> > that allows the user to control if HAL should be used or not.
> >
> > The properties dialog needs a setting to control the HAL usage and show
> > or hide the class of device box according to it.
>
> That sounds like over-engineering to me. What is the use case of the
> applet? If it's only going to be used on desktops, what's the matter
> with leaving the HAL support on? If the applet is to be used in embedded
> systems, surely those systems would make mofidications to the applet to
> fit their usage, and could turn off HAL support.
it is not over-engineered for people that don't have the HAL formfactor
setting to be used as base for the Bluetooth class of device. It also
makes the properties application simpler since it doesn't have to check
for HAL at all. It simply only sets a GConf value and applet acts
depending on this value.
> > > - Don't show the notification bubble when switching the bluetooth device
> > > on/off, and we're only showing the icon if a device is present. The icon
> > > appearing/disappearing should be enough
> >
> > We need to show when it goes back into connectable mode, because that
> > happens if you use the discoverable timeout.
>
> Then we should save the mode before the change of mode_changed signal,
> and only popup the notification if the previous mode was discoverable.
Good idea. Was actually to lazy to do it by myself. Then we can also
change the wording to discoverable/non-discoverable.
Regards
Marcel
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-02-24 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 23:31 [Bluez-devel] Another bluez-gnome patch Bastien Nocera
2007-02-24 15:43 ` Marcel Holtmann
2007-02-24 17:11 ` Bastien Nocera
2007-02-24 17:25 ` Marcel Holtmann [this message]
2007-02-26 1:03 ` Bastien Nocera
2007-02-26 9:24 ` Marcel Holtmann
2007-02-26 10:28 ` Bastien Nocera
2007-02-26 10:32 ` 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=1172337927.11537.19.camel@violet \
--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