stanfy/goro

Android library for organizing your asynchronous tasks in queues

goro's Issues

Make Goro instance used by GoroService injectable

It will allow to choose whether you want to use the main Goro instance directly (in a syncadapter, for example), or use something like BoundGoro in an Activity to pass jobs to the service context.

Release Goro 3.0

Main goals:

• get rid of bindOneshot()
• make Goro instance injectable in the service
• better Rx integration (implement a shceduler)
• logging

Service binding and scheduling from 'working' thread

BoundGoroImpl uses onServiceConnected which is always called in MainThread by Android. In the same time, schedule(...) could be called from any thread. And in case bindOneshot onServiceConnected could be called even before schedule puts future into postponed - in this case, future would never start.

Quick ugly fix is here almozavr@76a17c8 - I think it's no good to be merged into library, but I want to start a discussion.

Queues logging

Proposal.

Queues can be visualized

name   | processing | line
-----------------------------------------------
queue1 | task3      | task1 <- task2
queue2 | task10     | task43 <- task42 <- task0

We can dump the state with goro.dump(Writer).
Also there is a Dumper implements GoroListener that dumps the state whenever task is added/started/finished.
GoroService has static setDebug(true|false) method that leads to registering Dumper in debug mode.

Support multi-process task scheduling

Current Goro implementation heavily relies on the fact that GoroService is in the same process.

The check here:
https://github.com/stanfy/goro/blob/v3.0.0-RC3/goro/src/main/java/com/stanfy/enroscar/goro/Goro.java#L26

which is invoked here:
https://github.com/stanfy/goro/blob/v3.0.0-RC3/goro/src/main/java/com/stanfy/enroscar/goro/BoundGoro.java#L61

is required to obtain Goro instance from GoroService, which, in fact, was plugged in using GoroService.setup method.

But BoundGoro should send tasks to the GoroService, instead.

P.S. Currently, the only purpose of GoroService is to keep application alive, because it does not provide any IPC functions - it operates on the same Goro which was provided during setup.

Implement Rx scheduler

So that we can schedule an Observable work on Goro queue with scheduleOn or subscribeOn.

Share codeStyleSettings.xml

Provide .idea/codeStyleSettings.xml for easier contribution as there is non-default formatting.