[Bluez-devel] [gbluezconf] D-Bus client prototype

[Bluez-devel] [gbluezconf] D-Bus client prototype

[Claudio Takahasi]

Hi Marcel,

The first prototype is available at:
http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.01.tar.gz

Main features:
1. D-Bus PIN client
2. Search Dialog

Read to RELEASE_NOTES file to see the TODO list.

Suggestions are wellcome!
Please report bugs.

Regards,
Claudio.

PS: There are a lot of features not implemented or with some dependencies.
--
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]

Hi Claudio,

> The first prototype is available at:
> http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.01.tar.gz

it needed some love to make it compile, but I got it somehow. It also
depends on stuff that I haven't committed to the CVS so far. Especially
the missing/uninstalled <bluetooth/dbus.h> header file is a little bit
tricky.

> Main features:
> 1. D-Bus PIN client

I was able to test the PIN dialog and I really like that feature,
because the bluez-pin with D-Bus is basically unmaintained and I would
be happy if it disappears and every desktop or window manager comes with
its own PIN helper client.

> 2. Search Dialog

Wasn't able to get this working.

> Read to RELEASE_NOTES file to see the TODO list.

Let me give some comments on your TODO list.

We should definitiv use libnotify and only display the PIN dialog when
somebody clicked on the bubble. A flashing icon is nice, but I haven't
seen any other Gnome application using flashing icons for that. Might be
also against the HIG.

For the device icons you should contact the Tango team or the Gnome Art
team. Maybe they will come up with some.

The program should start even if no Bluetooth adapter would be found. In
this case only "About" and "Quit" should be visible.

For the configuration dialog and multiple adapters we should maybe use
the proposal from the bluetool screenshot (attached). I think it should
include a page for default/common settings for all devices. And then
some device specific parts that should have an extra check-box to
activate their settings or use the common ones.

Don't forget to make the device name and class of device configurable.

I am also a big fan of Okay/Cancel/Apply style dialogs, but the Gnome
standard is basically only Close (plus a help button) and we should
follow that style. The settings will become immediately active.

The search dialog shouldn't always start with zero devices if a previous
inquiry has already taken place. However I think for this we need to
implement a device cache inside hcid that could be requested up-front.

Besides the inactivity of the icon if no adapter is attached or if no
adapter is up, we maybe should change the icon if we have an active ACL
link. We can also use a different icon or animation if the device is
running an inquiry.

Anyhow, good work, I really like it and keep on coding.

What do you think about creating an own CVS repository for it.

Regards

Marcel


[-- Attachment #2: bluetools.png --]
[-- Type: image/png, Size: 238753 bytes --]

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Claudio Takahasi]

Hi Marcel,

There is a new version available. The search problem was fixed. It was
related to wrong inquiry result signature checking.
http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.02.tar.gz


On 12/20/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
>
> > The first prototype is available at:
> > http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.01.tar.gz
>

> it needed some love to make it compile, but I got it somehow. It also
> depends on stuff that I haven't committed to the CVS so far. Especially
> the missing/uninstalled <bluetooth/dbus.h> header file is a little bit
> tricky.
>
> > Main features:
> > 1. D-Bus PIN client
>
> I was able to test the PIN dialog and I really like that feature,
> because the bluez-pin with D-Bus is basically unmaintained and I would
> be happy if it disappears and every desktop or window manager comes with
> its own PIN helper client.
>
> > 2. Search Dialog
>
> Wasn't able to get this working.
[Claudio Takahasi]
Bug fixed!

>
> > Read to RELEASE_NOTES file to see the TODO list.
>
> Let me give some comments on your TODO list.
>
> We should definitiv use libnotify and only display the PIN dialog when
> somebody clicked on the bubble. A flashing icon is nice, but I haven't
> seen any other Gnome application using flashing icons for that. Might be
> also against the HIG.
[Claudio Takahasi]
Ok. I will investigate the best approach.

>
> For the device icons you should contact the Tango team or the Gnome Art
> team. Maybe they will come up with some.
>
> The program should start even if no Bluetooth adapter would be found. In
> this case only "About" and "Quit" should be visible.
[Claudio Takahasi]
I think it's better disable the options instead of remove the menu
item from the popup menu.

>
> For the configuration dialog and multiple adapters we should maybe use
> the proposal from the bluetool screenshot (attached). I think it should
> include a page for default/common settings for all devices. And then
> some device specific parts that should have an extra check-box to
> activate their settings or use the common ones.
[Claudio Takahasi]
Ok I will analize the bluetool approach. Multiple adapter is not a
common scenario. Therefore we need avoid display unnecessary infos. I
try re-design the "Configuration" dialog to make it more
user-friendly.

> Don't forget to make the device name and class of device configurable.
[Claudio Takahasi]
Device name changes is already possible. However change the device
class is not possible at the momment. We can extend the D-Bus services
soon.

>
> I am also a big fan of Okay/Cancel/Apply style dialogs, but the Gnome
> standard is basically only Close (plus a help button) and we should
> follow that style. The settings will become immediately active.
>
[Claudio Takahasi]
Ok. I will try follow the Gnome style.

> The search dialog shouldn't always start with zero devices if a previous
> inquiry has already taken place. However I think for this we need to
> implement a device cache inside hcid that could be requested up-front.
[Claudio Takahasi]
When the kernel/userspace communication interface becomes available we
can improve this dialog. The remote name needs be improved too, we can
use the textfile_get function to  retrieve cached remote names.

>
> Besides the inactivity of the icon if no adapter is attached or if no
> adapter is up, we maybe should change the icon if we have an active ACL
> link. We can also use a different icon or animation if the device is
> running an inquiry.
[Claudio Takahasi]
I try suggest new icons for address these cases next year.

>
> Anyhow, good work, I really like it and keep on coding.
>
> What do you think about creating an own CVS repository for it.
[Claudio Takahasi]
Do you mean create a new CVS root in BlueZ CVS repository? If yes, go ahead=
.
Currently, I am storing in my internal subversion server, but it's
better provide a public access.

>
> Regards
>
> Marcel

[Claudio Takahasi]
I will be on vacation until jan/15th. For D-Bus issues you can contact Edua=
rdo.
For GBluezConf, I will return the activities in the next year only.

--
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Marcel Holtmann]

Hi Claudio,

> > For the device icons you should contact the Tango team or the Gnome Art
> > team. Maybe they will come up with some.
> >
> > The program should start even if no Bluetooth adapter would be found. In
> > this case only "About" and "Quit" should be visible.
> 
> I think it's better disable the options instead of remove the menu
> item from the popup menu.

I would prefer to switch the visibility off, but you might check the
Gnome HIG guidelines for this.

> > For the configuration dialog and multiple adapters we should maybe use
> > the proposal from the bluetool screenshot (attached). I think it should
> > include a page for default/common settings for all devices. And then
> > some device specific parts that should have an extra check-box to
> > activate their settings or use the common ones.
> 
> Ok I will analize the bluetool approach. Multiple adapter is not a
> common scenario. Therefore we need avoid display unnecessary infos. I
> try re-design the "Configuration" dialog to make it more
> user-friendly.

I think that I gave this comment already. Having multiple adapters is
the normal situation. The special case is only one adapter. You can't
view it other way around.

> > Don't forget to make the device name and class of device configurable.
> 
> Device name changes is already possible. However change the device
> class is not possible at the momment. We can extend the D-Bus services
> soon.

We should extend, but only major and minor class. Not the services
classes, because they will depend on the registered services. Feel free
to send me a patch for it.

> > The search dialog shouldn't always start with zero devices if a previous
> > inquiry has already taken place. However I think for this we need to
> > implement a device cache inside hcid that could be requested up-front.
> 
> When the kernel/userspace communication interface becomes available we
> can improve this dialog. The remote name needs be improved too, we can
> use the textfile_get function to  retrieve cached remote names.

We can do already now if we know what is needed. Getting access to the
cached devices names must go also through D-Bus and actually I prefer to
make the name part of the device information. Proposals are welcome.

> > Besides the inactivity of the icon if no adapter is attached or if no
> > adapter is up, we maybe should change the icon if we have an active ACL
> > link. We can also use a different icon or animation if the device is
> > running an inquiry.
> 
> I try suggest new icons for address these cases next year.

Anyone from the Tango or Gnome Art team reading this mailing list?

> > What do you think about creating an own CVS repository for it.
> 
> Do you mean create a new CVS root in BlueZ CVS repository? If yes, go ahead.
> Currently, I am storing in my internal subversion server, but it's
> better provide a public access.

I will try to setup a repository for it next week, but be aware of that
the directory layout would be changed a lot ;)

> I will be on vacation until jan/15th. For D-Bus issues you can contact Eduardo.
> For GBluezConf, I will return the activities in the next year only.

Happy vacation.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Claudio Takahasi]

Hi Marcel,

A new prototype version is available at:
http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.04.tar.gz

Main features, enhancements and bug fixes:
1. Search dialog: devices are displayed based on "InquiryResult"
signal. The remote name is retrieved later.
2. Added gnome animation to indicate "inquiry in progress".
3. Changed buttons/menu according to Gnome UI guideline
4. Added internationalization
5. New icons based on gnome theme. (According to gnome art team, pango
project icons should not be used.)
6. When there isn't adapter available, menu options("Search" and
"Advanced Configuration" ) are disabled.
7. Added libnotify
8. Multiple search dialog double memory free fixed
9. UI glade file spplited to make the code mantainance easier

This code is compliant with bluez-utils-2.25
Suggestions are welcome!


Next planned actions:
1. Active connection dialog
2. Local Name
3. Set Connectable/Discoverable
4. Se Device class
5. Multiple adapter configuration


Regards,
Claudio.

On 12/21/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
>
> > > For the device icons you should contact the Tango team or the Gnome A=
rt
> > > team. Maybe they will come up with some.
> > >
> > > The program should start even if no Bluetooth adapter would be found.=
 In
> > > this case only "About" and "Quit" should be visible.
> >
> > I think it's better disable the options instead of remove the menu
> > item from the popup menu.
>
> I would prefer to switch the visibility off, but you might check the
> Gnome HIG guidelines for this.
>
> > > For the configuration dialog and multiple adapters we should maybe us=
e
> > > the proposal from the bluetool screenshot (attached). I think it shou=
ld
> > > include a page for default/common settings for all devices. And then
> > > some device specific parts that should have an extra check-box to
> > > activate their settings or use the common ones.
> >
> > Ok I will analize the bluetool approach. Multiple adapter is not a
> > common scenario. Therefore we need avoid display unnecessary infos. I
> > try re-design the "Configuration" dialog to make it more
> > user-friendly.
>
> I think that I gave this comment already. Having multiple adapters is
> the normal situation. The special case is only one adapter. You can't
> view it other way around.
>
> > > Don't forget to make the device name and class of device configurable=
.
> >
> > Device name changes is already possible. However change the device
> > class is not possible at the momment. We can extend the D-Bus services
> > soon.
>
> We should extend, but only major and minor class. Not the services
> classes, because they will depend on the registered services. Feel free
> to send me a patch for it.
>
> > > The search dialog shouldn't always start with zero devices if a previ=
ous
> > > inquiry has already taken place. However I think for this we need to
> > > implement a device cache inside hcid that could be requested up-front=
.
> >
> > When the kernel/userspace communication interface becomes available we
> > can improve this dialog. The remote name needs be improved too, we can
> > use the textfile_get function to  retrieve cached remote names.
>
> We can do already now if we know what is needed. Getting access to the
> cached devices names must go also through D-Bus and actually I prefer to
> make the name part of the device information. Proposals are welcome.
>
> > > Besides the inactivity of the icon if no adapter is attached or if no
> > > adapter is up, we maybe should change the icon if we have an active A=
CL
> > > link. We can also use a different icon or animation if the device is
> > > running an inquiry.
> >
> > I try suggest new icons for address these cases next year.
>
> Anyone from the Tango or Gnome Art team reading this mailing list?
>
> > > What do you think about creating an own CVS repository for it.
> >
> > Do you mean create a new CVS root in BlueZ CVS repository? If yes, go a=
head.
> > Currently, I am storing in my internal subversion server, but it's
> > better provide a public access.
>
> I will try to setup a repository for it next week, but be aware of that
> the directory layout would be changed a lot ;)
>
> > I will be on vacation until jan/15th. For D-Bus issues you can contact =
Eduardo.
> > For GBluezConf, I will return the activities in the next year only.
>
> Happy vacation.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


--
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Marcel Holtmann]

Hi Claudio,

> A new prototype version is available at:
> http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.04.tar.gz

you still depend on a "bluetooth/dbus.h" file that is not part of BlueZ
yet. Why don't you include a copy of it?

The error looks like this:

pair.c:41:28: error: bluetooth/dbus.h: No such file or directory
pair.c: In function '_dbus_pair_hci_signal_filter_cb':
pair.c:516: error: 'DEV_HCI_INTERFACE' undeclared (first use in this function)
pair.c:516: error: (Each undeclared identifier is reported only once
pair.c:516: error: for each function it appears in.)
...

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [gbluezconf] D-Bus client prototype

[Claudio Takahasi]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

Hi Marcel,

Use this attached file for now.
I will fix it in the next prototype.


Regards,
Claudio



On 1/26/06, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
>
> > A new prototype version is available at:
> > http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.04.tar.gz
>
> you still depend on a "bluetooth/dbus.h" file that is not part of BlueZ
> yet. Why don't you include a copy of it?
>
> The error looks like this:
>
> pair.c:41:28: error: bluetooth/dbus.h: No such file or directory
> pair.c: In function '_dbus_pair_hci_signal_filter_cb':
> pair.c:516: error: 'DEV_HCI_INTERFACE' undeclared (first use in this function)
> pair.c:516: error: (Each undeclared identifier is reported only once
> pair.c:516: error: for each function it appears in.)
> ...
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


--
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT

[-- Attachment #2: dbus.h --]
[-- Type: text/x-chdr, Size: 8565 bytes --]

/*
 *
 *  BlueZ - Bluetooth protocol stack for Linux
 *
 *  Copyright (C) 2004-2005  Marcel Holtmann <marcel@holtmann.org>
 *
 *
 *  This program is free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with this program; if not, write to the Free Software
 *  Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
 *
 */

#define __END_SIG__ DBUS_TYPE_INVALID_AS_STRING

#define BASE_PATH		"/org/bluez"
#define BASE_INTERFACE		"org.bluez"

#define DEVICE_PATH		BASE_PATH "/Device"
#define DEVICE_INTERFACE	BASE_INTERFACE ".Device"

#define MANAGER_PATH		BASE_PATH "/Manager"
#define MANAGER_INTERFACE	BASE_INTERFACE ".Manager"

#define ERROR_INTERFACE		BASE_INTERFACE ".Error"

#define MANAGER_PATH_MASK	(1 << 15)
#define DEVICE_PATH_MASK	(1 << 14)

/* /org/bluez/Manager */
#define MANAGER_ROOT_ID		MANAGER_PATH_MASK

/* /org/bluez/Device */
#define DEVICE_ROOT_ID		DEVICE_PATH_MASK

/* E.g. /org/bluez/Device/hci0 */
#define DEVICE_PATH_ID		(DEVICE_PATH_MASK | 0x0001)

/* E.g. /org/bluez/Device/hci0/Controller */
#define HCI_PATH_ID		(DEVICE_PATH_MASK | 0x0002)

#define INVALID_PATH_ID		0xFFFF
#define INVALID_DEV_ID		0xFFFF

/*======================================================================== 
    BlueZ D-Bus Manager service definitions "/org/bluez/Manager"
 *========================================================================*/

#define MGR_DEVICE_LIST		"DeviceList"
#define MGR_DEFAULT_DEVICE	"DefaultDevice"
#define MGR_INIT		"Init"

/* Enable/Disable services controller, pan, serial, ... */
#define MGR_ENABLE		"Enable"
#define MGR_DISABLE		"Disable"

/* Signatures */

#define MGR_GET_DEV_SIGNATURE			__END_SIG__

/* DeviceList Reply: a(devname, addr, type, up/down, a(flags)) - all types strings */
#define MGR_GET_DEV_REPLY_SIGNATURE		DBUS_TYPE_ARRAY_AS_STRING \
						DEV_GET_DEV_REPLY_STRUCT_SIGNATURE \
						__END_SIG__

#define MGR_GET_DEV_REPLY_STRUCT_SIGNATURE	DBUS_STRUCT_BEGIN_CHAR_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_ARRAY_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						DBUS_STRUCT_END_CHAR_AS_STRING \
						__END_SIG__

#define MGR_DEFAULT_DEV_SIGNATURE		__END_SIG__


/* Signals sent in the Manager path */
#define BLUEZ_MGR_DEV_ADDED		"DeviceAdded"
#define BLUEZ_MGR_DEV_REMOVED		"DeviceRemoved"


/*======================================================================== 
    BlueZ D-Bus Device path definitions "/org/bluez/Device"
 *========================================================================*/

/* Interfaces implemented in the "/org/bluez/Device" path */
#define BLUEZ_HCI			"Controller"
#define DEV_HCI_INTERFACE		DEVICE_INTERFACE "." BLUEZ_HCI

/* Control interface signals */
#define BLUEZ_HCI_INQ_START		"InquiryStart"
#define BLUEZ_HCI_INQ_COMPLETE		"InquiryComplete"
#define BLUEZ_HCI_INQ_RESULT		"InquiryResult"
#define BLUEZ_HCI_REMOTE_NAME		"RemoteName"
#define BLUEZ_HCI_REMOTE_NAME_FAILED	"RemoteNameFailed"
#define BLUEZ_HCI_AUTH_COMPLETE		"AuthenticationComplete"
#define BLUEZ_HCI_DISCONN_COMPLETE      "DisconnectionComplete"

/* Control interface methods */
#define HCI_PERIODIC_INQ		"PeriodicInquiry"
#define HCI_CANCEL_PERIODIC_INQ		"CancelPeriodic"
#define HCI_INQ				"Inquiry"
#define HCI_CANCEL_INQ			"CancelInquiry"
#define HCI_ROLE_SWITCH			"RoleSwitch"
#define HCI_REMOTE_NAME			"RemoteName"
#define HCI_CONNECTIONS			"Connections"
#define HCI_AUTHENTICATE		"Authenticate"

/* Control interface methods */
#define DEV_UP				"Up"
#define DEV_DOWN			"Down"
#define DEV_SET_PROPERTY		"SetProperty"
#define DEV_GET_PROPERTY		"GetProperty"

#define DEV_PROPERTY_AUTH		"auth"
#define DEV_PROPERTY_ENCRYPT		"encrypt"
#define DEV_PROPERTY_SECMGR		"secmgr"
#define DEV_PROPERTY_PISCAN		"piscan"
#define DEV_PROPERTY_PSCAN		"pscan"
#define DEV_PROPERTY_ISCAN		"iscan"
#define DEV_PROPERTY_PTYPE		"ptype"
#define DEV_PROPERTY_LM			"lm"
#define DEV_PROPERTY_LP			"lp"
#define DEV_PROPERTY_NAME		"name"
#define DEV_PROPERTY_CLASS		"class"
#define DEV_PROPERTY_VOICE		"voice"
#define DEV_PROPERTY_IAC		"iac"
#define DEV_PROPERTY_INCMODE		"incmode"
#define DEV_PROPERTY_INCTYPE		"inctype"
#define DEV_PROPERTY_INCPARMS		"incparms"
#define DEV_PROPERTY_PAGEPARMS		"pageparms"
#define DEV_PROPERTY_PAGETO		"pageto"
#define DEV_PROPERTY_AFHMODE		"afhmode"
#define DEV_PROPERTY_ACLMTU		"aclmtu"
#define DEV_PROPERTY_SCOMTU		"scomtu"
#define DEV_PROPERTY_PUTKEY		"putkey"
#define DEV_PROPERTY_DELKEY		"delkey"
#define DEV_PROPERTY_DEV_INFO		"info"

#define DEV_UP_SIGNATURE			__END_SIG__
#define DEV_DOWN_SIGNATURE			__END_SIG__
#define DEV_RESET_SIGNATURE			__END_SIG__
#define DEV_SET_PROPERTY_SIGNATURE_1		DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_BOOLEAN_AS_STRING \
						__END_SIG__
#define DEV_SET_PROPERTY_SIGNATURE_2		DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_STRING_AS_STRING \
						__END_SIG__
#define DEV_SET_PROPERTY_SIGNATURE_3		DBUS_TYPE_STRING_AS_STRING \
						DBUS_TYPE_UINT16_AS_STRING \
						__END_SIG__

#define DEV_GET_PROPERTY_SIGNATURE		DBUS_TYPE_STRING_AS_STRING \
						__END_SIG__

#define HCI_PERIODIC_INQ_SIGNATURE			DBUS_TYPE_BYTE_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							__END_SIG__

#define HCI_PERIODIC_INQ_EXT_SIGNATURE			DBUS_TYPE_BYTE_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_TYPE_UINT32_AS_STRING \
							__END_SIG__

#define HCI_CANCEL_PERIODIC_INQ_SIGNATURE		__END_SIG__

#define HCI_INQ_SIGNATURE				__END_SIG__

#define HCI_INQ_EXT_SIGNATURE				DBUS_TYPE_BYTE_AS_STRING \
							DBUS_TYPE_UINT32_AS_STRING \
							__END_SIG__

#define HCI_CANCEL_INQ_SIGNATURE			__END_SIG__

#define HCI_ROLE_SWITCH_SIGNATURE			DBUS_TYPE_STRING_AS_STRING \
							DBUS_TYPE_BYTE_AS_STRING \
							__END_SIG__

#define HCI_REMOTE_NAME_SIGNATURE			DBUS_TYPE_STRING_AS_STRING \
							__END_SIG__

#define HCI_CONNECTIONS_SIGNATURE			__END_SIG__

#define HCI_CONN_INFO_STRUCT_SIGNATURE			DBUS_STRUCT_BEGIN_CHAR_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_TYPE_STRING_AS_STRING \
							DBUS_TYPE_BYTE_AS_STRING \
							DBUS_TYPE_BYTE_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_TYPE_UINT32_AS_STRING \
							DBUS_STRUCT_END_CHAR_AS_STRING \
							__END_SIG__

#define HCI_DEVICE_STRUCT_SIGNATURE			DBUS_STRUCT_BEGIN_CHAR_AS_STRING \
							DBUS_TYPE_STRING_AS_STRING \
							DBUS_TYPE_STRING_AS_STRING \
							DBUS_STRUCT_END_CHAR_AS_STRING \
							__END_SIG__

#define HCI_INQ_REPLY_SIGNATURE				DBUS_STRUCT_BEGIN_CHAR_AS_STRING \
							DBUS_TYPE_STRING_AS_STRING \
							DBUS_TYPE_UINT32_AS_STRING \
							DBUS_TYPE_UINT16_AS_STRING \
							DBUS_STRUCT_END_CHAR_AS_STRING \
							__END_SIG__

#define HCI_AUTHENTICATE_SIGNATURE			DBUS_TYPE_STRING_AS_STRING \
							__END_SIG__


/* BLUEZ_DBUS_ERROR 
 * EFailed error messages signature is : su
 * Where the first argument is a string(error message description),
 * the last  is a uint32 that contains the error class(system, dbus or hci). */

/* Error code offsets */
#define BLUEZ_EBT_OFFSET		(0x00000000) /* see Bluetooth error code */
#define BLUEZ_EBT_EXT_OFFSET		(0x00000100)
#define BLUEZ_EDBUS_OFFSET		(0x00010000)
#define BLUEZ_ESYSTEM_OFFSET		(0x00020000)
#define BLUEZ_EFUTURE_OFFSET		(0x00040000)

/* D-Bus error code, class BLUEZ_EDBUS_OFFSET */
#define BLUEZ_EDBUS_UNKNOWN_METHOD	(0x01 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_WRONG_SIGNATURE	(0x02 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_WRONG_PARAM		(0x03 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_RECORD_NOT_FOUND	(0x04 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_NO_MEM   		(0x05 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_CONN_NOT_FOUND	(0x06 + BLUEZ_EDBUS_OFFSET)
#define BLUEZ_EDBUS_UNKNOWN_PATH	(0x07 + BLUEZ_EDBUS_OFFSET)

/* D-Bus error code, class BLUEZ_ESYSTEM_OFFSET */
#define BLUEZ_ESYSTEM_ENODEV		(ENODEV + BLUEZ_ESYSTEM_OFFSET)

/* BLUEZ_DBUS_ERR_NO_MEMORY */
#define BLUEZ_DBUS_ERR_NO_MEMORY_STR	"No memory"