Closed GoogleCodeExporter closed 9 years ago
We did a bit of brainstorming and we came up with the following design
decisions:
- Support both time and distance based tasks.
-- There should be just one class that does all scheduling both time and
distance based.
- Isolate Task logic from all scheduling logic.
- Remove dependency on TrackRecordingService on the Tasks.
-- We should introduce an interface for the Service.
- Make the interface for the TrackRecordingService as clean as possible.
-- The service should only see three methods:
--- scheduleAll()/restartAll()
--- cancelAll()
--- setFrequencyFor(Task t, Frequency f);
---- Where Task is an enum which a factory knows how to create the right task
type.
---- Frequency is a type that can encode time, distance and other frequency
types.
- Support dependency injection at as many levels as possible.
Original comment by sandordo...@google.com
on 24 Nov 2010 at 9:41
I'm interested in working on this refactoring, unless someone is already doing
it or wants to do it :)
Original comment by ba...@google.com
on 29 Nov 2010 at 5:27
I started working on unifying this code. Please let me know what you think of
these changes:
http://code.google.com/r/sandordornbush-staging/source/detail?r=2732fbbc000c3f8c
9ea14679a64409853beed9ae
They are still initial and I would like comments to know if I am going in the
right direction.
Original comment by sandordo...@google.com
on 7 Dec 2010 at 5:56
Original comment by sandordo...@google.com
on 6 Jan 2011 at 11:54
Original comment by sandordo...@google.com
on 12 Apr 2011 at 3:11
Original issue reported on code.google.com by
sandordo...@google.com
on 19 Nov 2010 at 10:48