ProcDispatcher: preliminary implementation

[Ichthyostega]

• build a usable first version of the ProcDispatcher component to schedule commands against the session, sequentially, in a dedicated thread.
• also add the ability to control ProcDispatcher's life-cycle, which means to start and stop this »session loop thread«
• allow for temporarily halting command dispatch

[Ichthyostega]

if someone wants to work on this: I'd be happy if something happens on this frontier. Please make sure you understand the design I made for this topic and the interplay with the already implemented command frontend. (read: please ask me to clarify any questions). Otherwise we're bound to waste a lot of effort here.

[Ichthyostega]

OK, so I've targetted this myself now.

Here goes one of the rare tasks, which Someone^TM could have done in parallel to the main thread of development...

[Ichthyostega]

TODO: also draft a test function in command-use2-test.cpp, to document the integrated usage

[Ichthyostega]

TODO: still need to care for consistent wake-up / notification on state changing operations

beyond that, an initial implementation of the processing loop and command queue is in place, together with the necessary control logic. Moreover, the public interface to the session, the SessionCommandService has been wired to be managed and backed by the ProcDispatcher

[Ichthyostega]

Work done -- changing to meta

In the last weeks, I have laid the foundations to run the session as a subsystem within the global application.
The Command handling framework was re-visited and wired up into a public facade interface to dispatch commands.

A lot of further sub-tasks remain to be done yet, in order to complete a preliminary session implementation, and thus
I'll turn this ticket into a meta ticket, to track further progress in that area.

[Ichthyostega]

mylyn/context/zip

[Ichthyostega]

reorganise dependencies to reflect the fact, that ProcDispatcher is basically finished for now

[Ichthyostega]

mylyn/context/zip

[Ichthyostega]

💡Note: since the three Layers within the Lumiera Architecture have been renamed some time ago, and especially the former »Proc-Layer« is called »Steam-Layer«, also this component is now known as SteamDispatcher

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin