Schoumi/BLE_API
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
BLE_API/module.json

34 lines
693 B
JSON
Raw Normal View History

switch to a yotta layout
2015-06-19 12:37:31 +00:00
{
"name": "ble",
Release 0.4.8 ============= * Introduce an Instance() class method to BLE to allow access to the BLE singleton(s) using instanceID. Calling BLE::Instance() is preferable to constructing a BLE object directly because Instance() returns references to internally created singletons. * We've added an initial prototype for a yotta-config based initialization for BLE transports. It is conceivable to have multiple BLE transports available to a system concurrently in which case Instance() can be passed an instanceID. There's also a BLE::NUM_INSTANCES--instanceID passed to Instance() should be less than NUM_INSTANCES for the returned BLE singleton to be useful. The config system now allows the target to specify multiple BLE instances. BLE::Instance() and BLE constructor rely upon a static array of initializers to create actual BLE transport instances. A description of these instances and initializers is supposed to be put in some .json file contributing to yotta's configuration (typically the target.json). Here's a sample: "config": { ... "ble_instances": { "count": 1, "0" : { "initializer" : "createBLEInstance" } } } Refer to http://yottadocs.mbed.com/reference/config.html. Note: The configuration system is currently experimental. Some of the behaviour described below may change in backwards-incompatible ways with minor updates to yotta. The use of this feature is optional. Initialization would continue to work like before as long as there is a default createBLEInstance() method available. * We've updated our support for Google's Eddystone beacon by adding the EddystoneConfigService. * Added onConnection() and onDisconnection() now append to a callback chain internally. Please note that this has also changed the callbackType for onDisconnection; resulting in a minor breaking change for API. All previous programs using onDisconnection() would need to adapt. * Handle the case of a NULL transport pointer for BLE. * We now disallow copy constructor and assignment operator for BLE.
2015-09-29 08:33:30 +00:00
"version": "0.4.8",
switch to a yotta layout
2015-06-19 12:37:31 +00:00
"description": "The BLE module offers a high level abstraction for using Bluetooth Low Energy on multiple platforms.",
"keywords": [
"Bluetooth",
"BLE"
],
"author": "Rohit Grover",
"repository": {
host repository has been renamed to github/ARMmbed/ble.
2015-08-07 14:29:34 +00:00
"url": "git@github.com:ARMmbed/ble.git",
switch to a yotta layout
2015-06-19 12:37:31 +00:00
"type": "git"
},
"homepage": "http://mbed.org/ble",
"licenses": [
{
"url": "https://spdx.org/licenses/Apache-2.0",
"type": "Apache-2.0"
}
],
version v0.4.3
2015-07-22 09:14:56 +00:00
"dependencies": {},
switch to a yotta layout
2015-06-19 12:37:31 +00:00
"targetDependencies": {
"nrf51822": {
depend on an updated version of nRF51822 which provides event handling through minar.
2015-08-13 10:08:32 +00:00
"ble-nrf51822": "~0.4.7"
module.json: depend on mbed-classic only for mbed-classic builds.
2015-07-13 09:05:56 +00:00
},
"mbed-classic": {
version v0.4.3
2015-07-22 09:14:56 +00:00
"mbed-classic": "~0.0.1"
add yotta dependency for mbed-core
2015-08-07 14:50:03 +00:00
},
Use mbed-os as a target dependency. This will be provided by the target configs.
2015-08-13 10:03:04 +00:00
"mbed-os": {
update module.json to depend on mbed-drivers instead of mbed-core
2015-08-10 07:36:41 +00:00
"mbed-drivers": "*"
switch to a yotta layout
2015-06-19 12:37:31 +00:00
}
}
Release 0.4.8 ============= * Introduce an Instance() class method to BLE to allow access to the BLE singleton(s) using instanceID. Calling BLE::Instance() is preferable to constructing a BLE object directly because Instance() returns references to internally created singletons. * We've added an initial prototype for a yotta-config based initialization for BLE transports. It is conceivable to have multiple BLE transports available to a system concurrently in which case Instance() can be passed an instanceID. There's also a BLE::NUM_INSTANCES--instanceID passed to Instance() should be less than NUM_INSTANCES for the returned BLE singleton to be useful. The config system now allows the target to specify multiple BLE instances. BLE::Instance() and BLE constructor rely upon a static array of initializers to create actual BLE transport instances. A description of these instances and initializers is supposed to be put in some .json file contributing to yotta's configuration (typically the target.json). Here's a sample: "config": { ... "ble_instances": { "count": 1, "0" : { "initializer" : "createBLEInstance" } } } Refer to http://yottadocs.mbed.com/reference/config.html. Note: The configuration system is currently experimental. Some of the behaviour described below may change in backwards-incompatible ways with minor updates to yotta. The use of this feature is optional. Initialization would continue to work like before as long as there is a default createBLEInstance() method available. * We've updated our support for Google's Eddystone beacon by adding the EddystoneConfigService. * Added onConnection() and onDisconnection() now append to a callback chain internally. Please note that this has also changed the callbackType for onDisconnection; resulting in a minor breaking change for API. All previous programs using onDisconnection() would need to adapt. * Handle the case of a NULL transport pointer for BLE. * We now disallow copy constructor and assignment operator for BLE.
2015-09-29 08:33:30 +00:00
}
Reference in a new issue Copy permalink