All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Huang <ashuang@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Documentation for development
Date: Fri, 22 Apr 2005 02:56:02 -0400	[thread overview]
Message-ID: <ef9938ec05042123566efacaad@mail.gmail.com> (raw)
In-Reply-To: <200504201931.06626.alan@mizrahi.com.ve>

If all you want is simple communication, then you may want to look at
the various JSR-82 implementations that are written for Linux.
rococosoft impronto, avetana, and javabluetooth.org are three
implementations you could try.

If you like python, you might be interested in pybluez

>From what you're describing, it's unlikely that you actually need to
code in C.  However, if you insist on doing so, you're not going to
find official documentation or APIs.  I've written some introductory
material that you might find helpful.

http://csail.mit.edu/~albert/misc/chap4.pdf

It's a work in progress, and I welcome feedback.

Regards,
Albert

On 4/20/05, Alan Mizrahi <alan@mizrahi.com.ve> wrote:
> El Wed 20 Apr 2005 5:29 am, Marcel Holtmann escribi=F3:
> > Hi Alan,
> >
> > > I want to make a program that communicates with my cellphone through
> > > bluetooth.
> > >
> > > I already installed and configured the bluez packages, but I can't fi=
nd
> > > the developers documentation, can anybody point me to the right place=
?
> >
> > the question is what kind of communication do you mean?
> >
>=20
> Just basic synchronous communication.  I don't intend to transfer files, =
my
> project is to be able to control a program from the cellphone (something =
like
> RPC).  Maybe the cellphone will get some feedback from the commands too.
>=20
> The cellphone program will be written in java-midp and the computer part =
in C.
>=20
> So what do you suggest?
> Is there any documentation I can read about bluetooth development?
>=20
> Regards,
>=20
> Alan
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime in=
fo,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2005-04-22  6:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  2:37 [Bluez-devel] Documentation for development Alan Mizrahi
2005-04-20  3:04 ` gao.yingbin
2005-04-20  9:29 ` Marcel Holtmann
2005-04-20 23:31   ` Alan Mizrahi
2005-04-20 23:48     ` Marcel Holtmann
2005-04-21 13:21     ` ligi
2005-04-22  6:56     ` Albert Huang [this message]

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=ef9938ec05042123566efacaad@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 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.