From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] D-Bus patching session opened
Date: Thu, 22 Sep 2005 16:28:25 +0200 [thread overview]
Message-ID: <1127399305.5344.36.camel@blade> (raw)
Hi,
after I dropped the D-Bus 0.23 API support it is now time to really play
with the integration of D-Bus support into hcid and other daemons. This
is the first step into creating a full D-Bus aware bluetoothd in the
future.
I like to see some more D-Bus enhancements now and Claudio already
started and he's working hard in explaining his work and making me
happy. So please help him and review his code and send small patches to
make the D-Bus experience better. I think about making the D-Bus a core
dependency of bluez-utils. Does anybody have any arguments against it?
Next thing that I like to see are some Python applications that are
using GTK+ and D-Bus for a graphical interface to BlueZ. For that I
think about creating a bluez-python package. Therefor we need people who
are writing the code and other people who are creating some nice fancy
icons and graphics for it. First thing should be a D-Bus aware PIN
helper written completely in Python.
There exists a job/task for everyone :)
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-09-22 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 14:28 Marcel Holtmann [this message]
2005-09-22 19:13 ` [Bluez-devel] D-Bus patching session opened Claudio Takahasi
2005-09-22 19:55 ` 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=1127399305.5344.36.camel@blade \
--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 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.