cpfeiffer a1cb246e27 Add and use a "client interface" for the actions of the service ... Previously, the DeviceCommunicationService was invoked directly, via Intent intent = new Intent(foo, bar); intent.setExtra(EXTRA_BAZ, baz); startService(...); and this was scattered throughout GadgetBridge. Now there is a "frontend" available, so that you can call the service more easily, like GBApplication.deviceService().connect(); For a start, this client interface (DeviceService) actually implements the same interface (EventHandler) as the receiving side (DeviceSupport). This may change in the future. This will also make testing much easier, because we can use this client interface to invoke the test service as well.		2015-08-21 01:03:57 +02:00
..
activities	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
adapter	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
database	Some initial fixes found by static analysis #92	2015-08-16 00:17:16 +02:00
deviceevents	Pebble: blindly implement missing parts for app installation on FW 3.x	2015-08-16 00:32:36 +02:00
devices	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
externalevents	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
impl	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
model	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
service	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
util	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
GBApplication.java	Add and use a "client interface" for the actions of the service	2015-08-21 01:03:57 +02:00
GBException.java	Refactoring of database access	2015-08-03 01:21:44 +02:00