W3C home > Mailing lists > Public > public-web-bluetooth@w3.org > August 2014

Re: Notes from meeting between Chrome and Mozilla folks

From: Marcos Caceres <marcos@marcosc.com>
Date: Thu, 7 Aug 2014 14:21:25 -0400
To: Jeffrey Yasskin <jyasskin@google.com>
Cc: public-web-bluetooth <public-web-bluetooth@w3.org>
Message-ID: <etPan.53e3c3a6.6ceaf087.16a@Marcoss-MacBook-Pro.local>



On August 5, 2014 at 10:01:35 PM, Jeffrey Yasskin (jyasskin@google.com) wrote:
> I've pushed the initial explainer to
> https://github.com/jyasskin/web-bluetooth/blob/gh-pages/explainer.md

I'm liking the general direction with promises, but please let's not do this:

```
bt.uuids.characteristic.heart_rate_measurement

```

(or let's not use UUID anywhere... they seem unnecessary - let's hide all that nonsense from developers) 

The way that the BT standard seems to define this stuff is really REALLY really crap... wow, so crap. We can do _a lot_ better by abstracting all the UUID crap away. 

Like: 

```JS
//note that this alias is already an indicator that the API is crappy, but whatever
var bt = navigator.bluetooth;

bt.requestDevice("heart_rate", {...options...}).then(
(hrMonitor) => {hrMonitor.onchange = (btDataEvent) => { 
   ... process data...   
}},
(boo) => alert("sorry, no heart rate for you."));
```

As an initial goal, can we map out the structure and architecture of the BlueTooth standard and parts we want to actually expose to the Web. Then we can work at simplifying the hell out of it in JS to get rid of most of the nonsense. It will also allow us to pick an choose the device classes we want to support initially and grow it from there, etc.  

It will also save us a bunch of cycles specifying stuff that we will then need to throw away later. 

> and filed a pull request for the initial
> chrome.bluetoothLowEnergy-based spec at
> https://github.com/jyasskin/web-bluetooth/pull/2. These don't match
> very well yet, which I'll be working on tomorrow. You can comment on
> the pull request if you think there's something I should change before
> merging it, or file issues if there's stuff we should discuss in the
> longer term.
>  
>  
>  
> On Tue, Aug 5, 2014 at 12:58 PM, Jeffrey Yasskin wrote:
> > The Chrome and Mozilla folks met yesterday about our plans for the web
> > bluetooth API. We have some rough notes at
> > https://docs.google.com/document/d/1ln1pVoeUpfWMJpR1JGE-wEL3yJBQdMWVvqGPzbaZnNE/edit?usp=sharing.  
> >
> > Today/tomorrow I'll migrate the draft explainer in that doc into
> > https://github.com/jyasskin/web-bluetooth and start fleshing out the
> > draft spec with matching APIs.
>  
>  
Received on Thursday, 7 August 2014 18:21:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:38:27 UTC