You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user / integrator I can easily get a MediaController or MediaBrowser instance.
Context
Creating a MediaController or a MediaBrowser can be a pain in the neck. The usage of ListenableFuture and knowing how to do it is a bit hard. Another problem is the custom function and listener added by Pillarbox than can be called from theses instances.
### Actual code to be done
val builder :MediaController.Builder=...
val future:ListenableFuture<MediaController> = builder.buildAsync()
future.addListener(() -> {
try {
val controller:MediaController= future.get()
// The session accepted the connection.
} catch (e:ExecutionException) {
if (e.getCause() isSecurityException) {
// The session rejected the connection.
}
}
}, ContextCompat.getMainExecutor())
}
Proposition
Integrators can fetch a custom MediaController with a suspend function.
scope.launch() {
val controller =PillarboxMediaController.Builder(...).buildAsnc()
doSomethingWithController(controller)
}
Acceptance criteria
MediaController instance can be created with one suspend function
MediaBrowser instance can be created with one suspend function.
Tasks
...
The text was updated successfully, but these errors were encountered:
As a user / integrator I can easily get a
MediaController
orMediaBrowser
instance.Context
Creating a
MediaController
or aMediaBrowser
can be a pain in the neck. The usage of ListenableFuture and knowing how to do it is a bit hard. Another problem is the custom function and listener added by Pillarbox than can be called from theses instances.### Actual code to be done
Proposition
Integrators can fetch a custom MediaController with a suspend function.
Acceptance criteria
MediaController
instance can be created with one suspend functionMediaBrowser
instance can be created with one suspend function.Tasks
The text was updated successfully, but these errors were encountered: