Hey Arsenij, Firstly, very nice feature you work on. Secondly, I just can tell from my experience what I think of two important things.
* During my development in my thesis, I sometimes made the same mistake again and again, thus not calling some piece of code from the SWT thread if it is needed. I mean, if there are such one- or bidirectional rules, they could also check if someone is calling something from the UI component, where in most cases it must be called from the SWT thread. I don't know, how complicated this would be and if it is even possible in the way I think. But it is just an idea (also for the 'Ausblick' part of your thesis ^^). I don't know it this issue is a frequent one in the Saros development but I think an important one. * Another rule was inspired from the MVC pattern. Is it possible to collect components into new components (component ui + x + y is the 'V' pattern/patternComponent, component concurrent + ? + .. is the controller/controllerComponent). It then looks like a tier application. These are just ideas. Even when they are not realizable or unusual perhaps they may be inspiring. Cheers, Damla
------------------------------------------------------------------------------
_______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
