From: Albert Huang <ashuang@gmail.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] some documentation for bluez
Date: Mon, 23 May 2005 01:44:51 -0400 [thread overview]
Message-ID: <ef9938ec0505222244400fe670@mail.gmail.com> (raw)
Hi all,
I've noticed that a fairly common question being asked around here is
"where is the API documentation?", and the answer is usually something
along the lines of "see the examples, then write some yourself". I've
written up a document that explains some of the basics, and may be
helpful for novice bluez developers.
http://people.csail.mit.edu/albert/pubs/ashuang-sm-thesis-2005.pdf
These are the parts that I think bluez programmers might care about
chapter 2 is a high level overview of bluetooth programming. No code.
chapter 3 is an introduction to developing applications in PyBluez
chapter 4 is an introduction to developing applications in bluez
Since it has an academic slant, it's nowhere near complete, and puts
heavy emphasis on some things that may seem insignificant. If there's
interest, though, I'd consider expanding chapter 4 into something to
point beginner developers to. Corrections and comments are also
welcome, as I am quite aware that I am by no means an expert at this
yet.
Regards,
Albert
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-05-23 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 5:44 Albert Huang [this message]
2005-05-23 6:01 ` [Bluez-devel] some documentation for bluez gao.yingbin
2005-05-23 10:17 ` 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=ef9938ec0505222244400fe670@mail.gmail.com \
--to=ashuang@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