From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-Bus interfaces
Date: Wed, 11 Feb 2004 15:35:03 +0100 [thread overview]
Message-ID: <1076510103.6281.162.camel@kalkyl.roxen.com> (raw)
In-Reply-To: <1076506129.2777.83.camel@pegasus>
Marcel,
ons 2004-02-11 klockan 14.28 skrev Marcel Holtmann:
> I think we should summarise what tasks an UI have to do and then design
> a D-Bus interface from it.
Here are some basic requirements, I think, for a Gnome Bluetooth Configuration
tool:
1. List devices currently attached.
2. Get info on devices currently attached (address, name, manufacturer,
type etc.)
3. Permanently configure device status (up/down).
4. Permanently configure device name.
5. Permanently configure device discoverability (Iscan? Pscan? Which?)
6. Permanently configure pair mode (allow/disallow).
7. List permanently stored configurations.
8. Remove permanently stored configurations.
9. List devices which are paired.
10. Remove devices which are paired.
11. Request the name for a device address, if available in the name cache.
12. Perform av device scan (this will also update the name cache).
13. Perform a pairing procedure (will update the name cache too).
14. Provide a one-time PIN during a pairing procedure.
(1) and (2) can possibly be solved without DBus, but the rest will require it.
Fredrik
next prev parent reply other threads:[~2004-02-11 14:35 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 18:35 [Bluez-devel] D-Bus support Marcel Holtmann
2004-02-08 18:51 ` Fredrik Noring
2004-02-08 19:09 ` Marcel Holtmann
2004-02-08 21:07 ` Fredrik Noring
2004-02-08 22:04 ` Marcel Holtmann
2004-02-08 22:33 ` Fredrik Noring
2004-02-08 21:28 ` [Bluez-devel] D-Bus interfaces Fredrik Noring
2004-02-08 21:54 ` Marcel Holtmann
2004-02-08 22:15 ` Fredrik Noring
2004-02-08 22:31 ` Marcel Holtmann
2004-02-08 22:50 ` Fredrik Noring
2004-02-08 23:19 ` Marcel Holtmann
2004-02-08 23:51 ` Fredrik Noring
2004-02-09 0:38 ` Marcel Holtmann
2004-02-09 7:22 ` Fredrik Noring
2004-02-09 10:06 ` Marcel Holtmann
2004-02-09 10:22 ` Fredrik Noring
2004-02-09 10:38 ` Marcel Holtmann
2004-02-09 10:46 ` Fredrik Noring
2004-02-09 11:03 ` Marcel Holtmann
2004-02-09 11:53 ` Fredrik Noring
2004-02-09 13:01 ` Marcel Holtmann
2004-02-09 13:23 ` Fredrik Noring
2004-02-09 15:46 ` Marcel Holtmann
2004-02-09 16:05 ` Fredrik Noring
2004-02-09 16:30 ` Marcel Holtmann
2004-02-09 17:04 ` Fredrik Noring
2004-02-11 10:03 ` Fredrik Noring
2004-02-11 13:32 ` Marcel Holtmann
2004-02-11 14:05 ` Fredrik Noring
2004-02-11 16:45 ` Marcel Holtmann
2004-02-11 22:00 ` Fredrik Noring
2004-02-11 22:29 ` Marcel Holtmann
2004-02-11 22:33 ` Fredrik Noring
2004-02-11 12:32 ` Fredrik Noring
2004-02-11 13:28 ` Marcel Holtmann
2004-02-11 14:35 ` Fredrik Noring [this message]
2004-02-11 17:05 ` Marcel Holtmann
2004-02-11 22:25 ` Fredrik Noring
2004-02-11 22:42 ` Marcel Holtmann
2004-02-11 22:57 ` Fredrik Noring
2004-02-11 23:14 ` Marcel Holtmann
2004-02-11 23:29 ` Fredrik Noring
2004-02-11 23:36 ` Marcel Holtmann
2004-02-11 23:41 ` Fredrik Noring
2004-02-11 23:46 ` Marcel Holtmann
2004-02-08 23:15 ` Fred Schättgen
2004-02-16 14:46 ` Phil Blundell
2004-02-16 15:36 ` Marcel Holtmann
2004-02-16 15:41 ` Phil Blundell
2004-02-17 22:59 ` Marcel Holtmann
2004-02-17 23:38 ` Philip Blundell
2004-02-17 23:44 ` Marcel Holtmann
2004-02-17 23:49 ` Philip Blundell
2004-02-17 23:57 ` Marcel Holtmann
2004-02-18 0:08 ` Philip Blundell
2004-02-18 0:17 ` Marcel Holtmann
2004-02-18 0:29 ` Philip Blundell
2004-02-19 15:55 ` Fredrik Noring
2004-02-19 16:01 ` Fredrik Noring
2004-02-19 15:52 ` Fredrik Noring
2004-02-19 16:48 ` Phil Blundell
2004-02-20 4:04 ` Fredrik Noring
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=1076510103.6281.162.camel@kalkyl.roxen.com \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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