From: Dylan <jerry87905@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [GSoC 2008]bluez-python
Date: Tue, 29 Apr 2008 22:46:57 +0800 [thread overview]
Message-ID: <200804292246.57527.Jerry87905@gmail.com> (raw)
Greetings everyone,
I should send this earlier, ok....
First I wanna thank you guys for giving me this great opportunity. I believe
it will be a pleasure to work with Bluez Develop team.
My name is Li Dongyang and bluez-python is a high level python binding to
bluez using dbus-python. It will just face to Bluez 4.X API.
Currently we've encountred 2 problems.
One is about the mainloop.Many dbus and bluez operations need a mainloop,
and an option is let the user specify the mainloop they wanna use, and we
check the type of the mainloop, and import dbus.mainloop.glib(for gmainloop)
or dbus.mainloop.qt(for qt4 mainloop) and many other mainloops , and then set
it as the default mainloop.
Another is about the plugin system, when new plugin come out, an option is to
use org.freedesktop.DBus.Introspectable get the API xml, however, this makes
we difficult to modify the method. for example, we want DefaultHeadset() of
bluez-python return an object(not the dbus object) instance of AudioDevice or
Headset, not the dbus object path.
Anyone wanna discuss about bluez-python, fell free to mail me or ping me at
#bluez, my nick is missed(GMT +8)
Cheers
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2008-04-29 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200804292246.57527.Jerry87905@gmail.com \
--to=jerry87905@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).