public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Dongyang <jerry87905@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [GSoC2008]bluez-python status
Date: Fri, 1 Aug 2008 22:26:19 +0800	[thread overview]
Message-ID: <200808012226.20253.Jerry87905@gmail.com> (raw)

Hi, all
  This is Li Dongyang working on bluez-python
  And What's new from the last status report:
  1.a fix that can make async call with CreatePairedDevice(), user should pass 
reply_handler and error_handler
  The reply_handler will receive a Device instance as the parameter, the 
error_handler will receive an exception(our custom dbus exception, see 
errors.py) as the parameter.
  2.add the docstrings for all the methods, based on the docs in /doc/XXX-
api.txt
  3.still some doc work, like license headers, and AUTHORS, ChangeLog, README, 
COPYING file
  and a setup script to make python package
  What to be done is the plugin, My mentor and me are discussing which is the 
best way to represent it, and make it can handler new plugins in the future.
  Feel free to tell me if you have ideas about it ;-)
Cheers,
Li Dongyang

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-08-01 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 14:26 Li Dongyang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-29 16:22 [Bluez-devel] [GSoC2008]bluez-python status Li Dongyang

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=200808012226.20253.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