WebAPI/WebBluetooth: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 50: Line 50:
==== DBus on Linux and Android ====
==== DBus on Linux and Android ====


There are many ways to access DBus from code. On linux, gecko already uses the glib bindings for battery information on linux ([UPowerClient.cpp https://github.com/doublec/mozilla-central/blob/master/hal/linux/UPowerClient.cpp]).  
There are many ways to access DBus from code. On linux, gecko already uses the glib bindings for battery information on linux ([ https://github.com/doublec/mozilla-central/blob/master/hal/linux/UPowerClient.cpp UPowerClient.cpp]).
Android uses the low level DBus bindings, mainly made for writing language binding systems. This tends to create very complicated code, which even the DBus maintainers warn developers off of (See [DBus API Documentation http://dbus.freedesktop.org/doc/api/html/]).  
Android uses the low level DBus bindings, mainly made for writing language binding systems. This tends to create very complicated code, which even the DBus maintainers warn developers off of (See [http://dbus.freedesktop.org/doc/api/html/ DBus API Documentation]).  


On B2G, we'd like to avoid tying glib into the gecko build. We'll be using the [dbus-c++ http://gitorious.org/dbus-cplusplus] library on that platform in order to keep the dbus code simple and clean.
On B2G, we'd like to avoid tying glib into the gecko build. We'll be using the [http://gitorious.org/dbus-cplusplus dbus-c++] library on that platform in order to keep the dbus code simple and clean.


=== Links ===
=== Links ===
44

edits