From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Device type filter ideas
Date: Fri, 7 Mar 2008 19:36:13 +0100 [thread overview]
Message-ID: <DF35A68F-4B41-448D-9C12-BB4FACED2D57@holtmann.org> (raw)
In-Reply-To: <1204819758.2640.123.camel@cookie.hadess.net>
Hi Bastien,
> As can be seen after yesterday's commit, the device type filter in the
> selection widget is starting to get a bit long.
>
> How about putting the work of adding new filters onto applications
> instead?
I like to have something that GTK+ does with the File Dialog filters.
That would be the right approach.
> I can think that sendto would add filters for Phones, Printers, and
> computers, as those are the most likely type of devices that could
> have
> obex available.
We need a way to filter on service classes instead of major/minor
classes. Also we need some support for Extended Inquiry cases where
we would get a list of UUIDs for free during inquiry.
Before we extend the filters, we need to make the Device Selection
widget more generic. For example configureable title and be able to
hide the filters part. Take a lot at the current code for the wizard.
It looks ugly and is wrong in that context. Also in case of the wizard
we don't wanna show bonded and trusted devices at all. We already know
about them and wanna setup only new ones.
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
prev parent reply other threads:[~2008-03-07 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 16:09 [Bluez-devel] Device type filter ideas Bastien Nocera
2008-03-07 18:36 ` 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=DF35A68F-4B41-448D-9C12-BB4FACED2D57@holtmann.org \
--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