WebAPI/WebBluetooth: Difference between revisions

WebAPI/WebBluetooth (view source)

61 bytes added , 26 May 2012

44

edits

@@ Line 99: / Line 99: @@
 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 [http://dbus.freedesktop.org/doc/api/html/ DBus API Documentation]).
+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]). Even so, due to the [http://gitorious.org/dbus-cplusplus dbus-c++] library depending on exceptions (though the Chromium project is working on fixing that) and not wanting to fold in glib to B2G, we'll be using the low-level DBus API for B2G's WebBluetooth layer.
-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 ===