11 commits

Author	SHA1	Message	Date
Ichthyostega	6073df3554	Looper: other (better?) idea how to handle "builder dirty" automatically ... ...this means to turn Looper into a state machine. Yet it seems more feasible, since the DispatcherLoop has a nice checkpoint after each iteration through the while loop, and we'd keep that whole builder-dirty business completely confined within the Looper (with a little help of the DispatcherLoop) Let's see if the state transition logic can actually be implemented based just on such a checkpoint....?	2016-12-20 03:53:48 +01:00
Ichthyostega	14e0d65468	Looper: idea how to determine "builder dirty" ... ...just by offloading that task onto the CommandQueue, which happens to know when a new command is being scheduled	2016-12-20 03:18:03 +01:00
Ichthyostega	746866f5fc	Looper: draft requirements on logic for triggering the builder	2016-12-16 23:56:53 +01:00
Ichthyostega	b873f7025b	ProcDispatcher: mark some next tasks to care for	2016-12-16 23:26:56 +01:00
Ichthyostega	8ee08905b3	Looper: extend test coverage	2016-12-16 20:38:00 +01:00
Ichthyostega	30254da95f	Looper: implement core operation control logic	2016-12-16 19:21:06 +01:00
Ichthyostega	9c9e75ee01	Looper: define testcase regarding activity control	2016-12-16 18:40:29 +01:00
Ichthyostega	af92ed505b	Looper: implementation	2016-12-16 18:34:04 +01:00
Ichthyostega	be97473779	Looper: define first basic testcase	2016-12-16 18:23:46 +01:00
Ichthyostega	5fd65d6613	Looper: test setup	2016-12-16 18:09:51 +01:00
Ichthyostega	00077d0431	ProcDispatcher: decide on requirements and implementation structure (#1049)	2016-12-15 20:48:35 +01:00