From: Gael V. <gae...@no...> - 2009-02-02 17:18:21
|
On Mon, Feb 02, 2009 at 03:47:32PM +0000, Chris Walker wrote: > One of the things I liked about Gael's article was its discussion of > threading - separating the gui from the calculations from the data > acquisition. Thanks. Be aware that this is a rats nest, though, as threading is the best way to reveal all the subtleties of an event loop, and the various race conditions that you can have with it. The strong model/view separation that is implicit in Traits allows to hide the code making the view thread-safe in the Traits code updating implicitly the view. You can build these constraints in your multi-threaded application (I believe I touch a couple of words on this in my tutorial), but you have to be aware of the problems and the good patterns to answer them. To sum up, I am not saying this is uninteresting, on the contrary, I am just saying that such text is hard to write (which makes a good text even more interesting). My 2 cents, Gaël |