Re: official bluetooth plugin [closed]

[Inoa Koala <in...@gmail.com>]

I now understand why there is no official bluetooth plugin.

I did not mean to make demands, I thought my original message was a 
written as a proposal or enhancement. Clearly I was wrong.

| Possibly worth noting is that "Bluetooth" is a really amorphous thing.
| ...
| Do you want BT-PAN? BT-DUN? BT-OBEX? BT-FTP? BT-SERIAL?
|     -- Josh Soref

| We try to conform to W3C standards, and there is no w3c Bluetooth API
|   -- Shazron

| I am extremely critical of adding new APIs when our existing APIs 
aren't getting the support and attention that they | need.
|   -- Joe Bowser

In my mind it seemed rather simple. Simply use the key classes for 
android BluetoothSocket and BluetoothServerSocket.

http://developer.android.com/guide/topics/connectivity/bluetooth.html

In my mind IOS would have some similar API.

But as Soref has informed me, that is not the case. As Shazron and 
Bowser have put it, it's a problem of project philosophy.

On 19/11/2014 3:07 PM, Joe Bowser wrote:
> On Wed Nov 19 2014 at 11:57:34 AM Shazron <sh...@gmail.com> wrote:
>
>> Hi Inoa,
>> First off, please don't make demands, I mean it's just not polite,
>> especially if this is the first time you've posted here. There are various
>> reasons why we didn't create a Bluetooth plugin and it goes straight to
>> project philosophy. We try to conform to W3C standards, and there is no w3c
>> Bluetooth API (they are "working on it". still.). Barring that, we can
>> still propose one, and we have to work out compatibility with all the
>> platforms, and agree to an API.
>>
>>
> There's also the fact that there's the whole "cease to exist" thing.  There
> are numerous contributors who work on Bluetooth and BluetoothLE plugins for
> various platforms.  I feel that the community provides better support for
> third-party plugins than we do for the official plugins, and that the less
> "official" plugins we maintain, the better off the project is as a whole.
>
> As for the official plugins, it basically means that these plugins existed
> when we donated the project to the ASF.  We will keep maintaining these
> plugins until better alternatives exist either with it working directly in
> the WebView (eg Android Geolocation), or with a third-party replacement
> that has someone who really cares maintaining it.
>
> I am extremely critical of adding new APIs when our existing APIs aren't
> getting the support and attention that they need.  The first priority is
> core, and making sure that developers have options for basic features such
> as having a WebView that renders on the device they are targeting.
>
>
>> On Wed, Nov 19, 2014 at 11:34 AM, Inoa Koala <in...@gmail.com> wrote:
>>
>>> Yes, https://github.com/randdusing/BluetoothLE is interesting.
>>>
>>> But why is there no **official** bluetooth plugin for cordova that is
>> part
>>> of the Apache Software Foundation?
>>>
>>> I must write it? No one else has wanted to make an official bluetooth
>>> plugin for cordova?
>>>
>>> It puzzles me that "Apache Cordova is a platform for building native
>>> mobile applications using HTML, CSS and JavaScript" and yet there is no
>>> official bluetooth plugin.
>>>
>>>
>>> On 19/11/2014 2:23 PM, Jesse wrote:
>>>
>>>> ... because you haven't written it yet.
>>>> This one looks interesting: https://github.com/randdusing/BluetoothLE
>>>> I haven't used it though.
>>>>
>>>> @purplecabbage
>>>> risingj.com
>>>>
>>>> On Wed, Nov 19, 2014 at 11:02 AM, Inoa Koala <in...@gmail.com>
>> wrote:
>>>>   Hello cordova developpers,
>>>>> Why is there no official bluetooth plugin listed on
>>>>> http://cordova.apache.org/ ?
>>>>>
>>>>> Specifically, I wish to do Android to Android bluetooth communication.
>>>>>
>>>>> Instead one needs to use 3rd party plugins. Maybe they work but they
>> are
>>>>> not officially supported.
>>>>>
>>>>> Why is there no official bluetooth plugin that does:
>>>>> * IOS to IOS
>>>>> * Android to Android
>>>>> * IOS to other bluetooth device
>>>>> * Android to other bluetooth device
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>>>
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org

Re: official bluetooth plugin [closed]

[Josh Soref <js...@blackberry.com>]

Inoa Koala wrote:
>In my mind it seemed rather simple. Simply use the key classes for
>android BluetoothSocket and BluetoothServerSocket.

For reference, that's BT::SPP aka "BT-SERIAL" in my list.

While it may be something that someone might want, it certainly wasn't the
one I was expecting people to want.

But, I have different expectations about what one would do w/ BT.

Basically, it helps to understand the use case.

Why do you want a serial protocol? Are you trying to talk to a medical
device?
Are you trying to talk to another mobile-phone?
Are you trying to talk to a computer?

(There are w3c WGs/CGs investigating some specific Ucs, but w/o knowing
what yours are, it's hard to say much about the space.)

Btw. I don't go by my last name.

Josh


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org