public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Wizard patch
Date: Mon, 30 Jun 2008 19:27:00 -0300	[thread overview]
Message-ID: <2d5a2c100806301527y21f80385vc75acdf9da62029c@mail.gmail.com> (raw)
In-Reply-To: <035501c8dab3$5596b380$6701a8c0@freqonedev>

Hello David,

> I read the docs and when the code works as expected it is good enough.
> However, I have had a number of problems making the code work (partially
> implemented "experimental" 4.x features in release 3.33 and before).

You should first understand that the documentation in doc/ are dbus
specifications, they are not normal method calls or gobject signals.
You seems to be confused by using dbus-glib and not really knowing
what dbus is doing, we don't document how to use the API in terms of
language bindings, because it is open to the application developer to
choose between the bindings and the binding itself should document how
it map the different signatures.

> Also, figuring out how to handle some of the formats (e.g., the "dict"
> with variant) are a bit hard to figure out without a code example.  SO,
> I often have to dig into the actual code and figure out just what is
> going on.

See my point here, just because dbus-glib maps the signature a{sv}
(that is the real "dict") to a GHashTable using a GValue doesn't mean
any other binding will do the same. It's up to the binding to provides
this kind of documentation not the dbus API which should not be tied
to a single binding.

This tutorial should cover what you want:
http://dbus.freedesktop.org/doc/dbus-tutorial.html

-- =

Luiz Augusto von Dentz
Engenheiro de Computa=E7=E3o

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-06-30 22:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 19:05 [Bluez-devel] Wizard patch Michael Terry
2008-06-27 19:18 ` Michael Terry
2008-06-27 19:38 ` David Stockwell
2008-06-27 19:42   ` Michael Terry
2008-06-27 22:24     ` Marcel Holtmann
2008-06-27 22:23 ` Marcel Holtmann
2008-06-30 12:51   ` Michael Terry
2008-06-30 12:57     ` Marcel Holtmann
2008-06-30 13:20       ` Michael Terry
2008-06-30 14:07         ` Marcel Holtmann
2008-06-30 13:15   ` Michael Terry
2008-06-30 14:06     ` Marcel Holtmann
2008-06-30 15:57       ` Michael Terry
2008-06-30 16:03         ` Marcel Holtmann
2008-06-30 18:53           ` Michael Terry
2008-07-01  1:10             ` Marcel Holtmann
2008-07-09 14:28               ` Michael Terry
2008-08-19 17:33                 ` Michael Terry
2008-06-30 13:51   ` Michael Terry
2008-06-30 19:58     ` Michael Terry
2008-06-30 20:01       ` Michael Terry
2008-06-30 20:38         ` Bastien Nocera
2008-06-30 20:42         ` Mario Limonciello
2008-07-01  1:16     ` Marcel Holtmann
2008-06-30 15:48   ` Michael Terry
2008-07-01  1:24     ` Marcel Holtmann
2008-06-27 22:44 ` Bastien Nocera
     [not found]   ` <031301c8da4d$0bce3720$6701a8c0@freqonedev>
     [not found]     ` <1214813891.4435.149.camel@cookie.hadess.net>
2008-06-30 13:15       ` David Stockwell
2008-06-30 22:27         ` Luiz Augusto von Dentz [this message]
2008-07-01 18:56           ` David Stockwell

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=2d5a2c100806301527y21f80385vc75acdf9da62029c@mail.gmail.com \
    --to=luiz.dentz@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