Pipelined livre

[bilgili]

So, my pipelines are here:

Why did I do this ?

1. Dash is a nice library but control over it is a bit difficult and I had to rearchitecture Livre a lot ( maybe dash as well ). Understanding it takes a bit time until people gets used to it. I wanted to simplify this. It may not be simpler, you are going to tell me :)
2. Rearchitecture was needed to fix issues like: multiple windows under a node, cache overcommiting, etc.
3. I wanted a way of running some parts of the codes asynchronously under some control. Like the visible tree generation per root octree node etc, but using my previous algorithms.
4. I wanted to add easy ways of processing of data blocks ( filtering + adding information ) etc, and of course in paralellel.
5. Graphs are easier to grasp for people and with the pipeline you can create this graphs easily. There is type control over the connections in runtime so you cant go wrong. The type checking is based on c++11 typeindex and this can be discussed.
6. I want to gather different kinds of renderings together with Livre and the addition of those things into the code will be a bit more easier.
7. The connection mechanism is currently based on futures and it is a synchronization object based on two pieces. promise + future and futures here provides means to query, set and retrieve data. These copules are similar to publisher + subscriber, hpx futures so in the future it may be possible to extend using remote functions.

I am creating this pull req in order to discuss / change or even completely delete ( I am fine with it). I think at the end I really had a nice idea of using graph based algorithms and if we dont use it, I will make a library called "TaskTube" :) for my own things.

Do jump in if you want but I would like to go with a couple of people different regions of the code.

Known issue: On exit I am getting
21218.Main ../Collage/co/localNode.cpp:387 8284 0 connections open after close
21218.Main ../apps/livre/livre.cpp:90 8284 Assert: client->getRefCount() == 1 [Client still referenced by 7] in:
but I will have a look at it.

[eile]

ScopedMutex semantics and scoped code, please.

[rdumusc]

zzzz??? :-)

[rdumusc]

+1 for my part, someone else can give the +2. It is a large change - try to merge after careful testing and bug fixing :-)

[eile]

typo clas

Style: In doxygen I already see that this is the Executable class. I prefer:

'Base class for objects that can be executed by workers' , i.e., DRY.

[eile]

This is what I call a filter in the ISC document?

[bilgili]

I think so. It is independent from where it is being executed.

[eile]

Is there an overview on all the pipeline classes? Either some doxygen or UML diagram? I got lost in all the input/output filter/executor/port permutations.

[bilgili]

I am thinking about a presentation for it. I did not have time :)

[bilgili]

#188 implemented all functionality of this commit