On 2013-03-13, at 5:03 PM, Kyle Machulis <[email protected]> wrote:
> Hey! qDot here, FxOS systems engineer, ex robotics engineer, reluctant > arduino class teacher, etc etc etc > > So on FxOS currently, we've got RFCOMM sockets available in the low level > platform, but only in service of getting headsets and file transfer over > bluetooth working via DOM APIs. Not only that, they can only be accessed via > certified apps, meaning whatever we ship with the phone. So, not horribly > useful for external I/O boards. > > That said, I don't think it'd be a huge issue (not a trivial engineering > feat, but not huge either) to tack on raw bluetooth serial sockets, which is > what most platforms I'm familiar with use. I don't foresee us having > resources/need to do this internally any time soon, though. > > I'm not sure about what network APIs we're going to be exposing, but it could > be worth prototyping interfaces via network also. For BT LE I would be more interested in having an API similar to Apple's CoreBluetooth. It is a very nice high level API that basically allows you to do device discovery, connect to a device, read/write to/from a device. Here is a good blog about it: http://www.icapps.com/corebluetooth-unraveled/ And this is an example: http://developer.apple.com/library/mac/#samplecode/HeartRateMonitor/Listings/HeartRateMonitor_HeartRateMonitorAppDelegate_m.html#//apple_ref/doc/uid/DTS40011322-HeartRateMonitor_HeartRateMonitorAppDelegate_m-DontLinkElementID_4 Their API is very elegant and would map pretty well to what we do with async JS APIs I think. If we have this then for example Fitbit could write a FxOS app to talk to their digital scales and pedometers. It opens up so much cool stuff. S. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
