[Clusterviz-devel] Opinions on threadconn.py

[K. W. <k.w...@gm...>]

Hi,
in the last days I commited some code and introduced a new class 
threadconn. It should do all the thread management and communication.

In particular, the clustering algorithm class is now not derived von 
threading.Thread anymore. Instead, threadconn.start creates a new
Thread object by itself.

What's your opinion about all this? Do you think it's useful or does it 
make the things too complicated?

Personally, I don't like that the clusterdisplay class is still used by 
both threads, the changeAssignment und the updateCluster method by the 
clustering thread and all other methods by the gui thread. To resolve 
this, I suggest creating a new data class, which is shared by both 
threads and holds the data, the transformation matrix, and the history, 
but no display code. I think this could simplify the things: for 
instance, it would be easier to change the data set without restarting 
the program or to save/read history data.

What do you think about this suggestion? Would be nice if you encourage 
me a bit -- or stop me if you don't like it..

Kind regards,
Karsten.