From: Daniel Gollub <dgollub@suse.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper
Date: Mon, 28 May 2007 18:48:09 +0200 [thread overview]
Message-ID: <200705281848.09618.dgollub@suse.de> (raw)
In-Reply-To: <200705280939.31695.denis.kenzior@trolltech.com>
On Monday 28 May 2007 01:39:31 Denis KENZIOR wrote:
> As part of our work on Qtopia we've wrapped the BlueZ DBUS interface and
> some of the Bluetooth socket types in a nice Qt way. =A0We've also done s=
ome
> work on OBEX support in Qtopia 4.2, with much nicer API in Qtopia 4.3.
>
> Check out http://doc.trolltech.com/qtopia4.2/qtopiabluetooth.html. =A0If
> there are some things which can be used by KDE (beats duplicating effort),
> I can work on separating the Bluetooth classes as a separate Solutions
> package or something. =A0Same goes for OBEX support.
Sounds very interesting! =
I have to take a deeper look on the implementation of the BlueZ DBUS =
interface... is there any plan to wrap also BlueZ Service APIs like the Inp=
ut =
Service? Or is this already done?
Or you going to implement the Authorization Agent as well?
Actually i plan to implement all the services which are available by BlueZ =
... =
So it would be very interesting which BlueZ services get implemented/used b=
y =
Qtopia. Or should it be possible to make use of all services via =
QBluetoothAbstractService?
On which version of BlueZ will be Qtopia 4.3 based? bluez-utils 3.9 like =
Qtopia 4.2?
Are you going to keep the OBEX support or make use of the BlueZ transfer =
service in the future?
A separated package would be great...
best regards,
Daniel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-28 16:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 13:52 [Bluez-devel] Suggesting bluez_pinhelper Gilboa Davara
2007-05-27 16:36 ` Marcel Holtmann
2007-05-27 17:28 ` Gilboa Davara
2007-05-27 18:04 ` Marcel Holtmann
2007-05-27 18:35 ` Gilboa Davara
2007-05-28 8:29 ` Marcel Holtmann
2007-05-27 16:59 ` Petteri Räty
2007-05-27 17:31 ` Gilboa Davara
2007-05-27 17:48 ` Petteri Räty
2007-05-27 18:41 ` Gilboa Davara
2007-05-29 11:27 ` Stefan Seyfried
2007-05-29 12:45 ` Gilboa Davara
2007-05-27 23:19 ` Daniel Gollub
2007-05-27 23:39 ` Denis KENZIOR
2007-05-28 16:48 ` Daniel Gollub [this message]
2007-05-28 21:11 ` Denis KENZIOR
2007-05-28 22:21 ` Daniel Gollub
2007-05-28 8:29 ` Marcel Holtmann
2007-05-28 16:53 ` Daniel Gollub
2007-05-29 3:50 ` 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=200705281848.09618.dgollub@suse.de \
--to=dgollub@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.