TKTProcess and task as unity of execution discussion

[sbragagnolo]

In fact the original idea of tkt process is not to provide data to the dashboard, but to represent have a representation messageSend-based for the local pharo process. Not to be polymorphic with it, but to be polymorphic with, by example, remote process (maybe matra instance process?). to be able to use the same runners with different kind of processes. We should discuss about that, i still thinking is good approach.
As well, in the same approach of Tkt2, the idea was to keep the task execution as the minimal unit of execution, and the only object that should be allowed to do not work with this level of abstraction should be the tktprocess hierarchy, since it needs to really execute the things.

There are some incoherences, even in the tkt2 code, like the fact that there is a sameProcessRunner, when that should be something like tktlocalprocess. leaving to the runner the responsibilities of choosing the kind of process, spawn task executions from tasks, relating futures with the result of the processing and knowing how to deal with errors.

We should discuss about this as opening of the next milestone

[tinchodias]

Is Tkt2 already this repo's code?