Hi Yuriy, Loading a Moose model actually happens in a separate thread and you should be able to do other things in the meantime. However, it is true that the image becomes less responsive when doing that. Did you experience anything different?
Doru -- www.tudorgirba.com "Every thing has its own flow." > On 02.12.2013, at 19:59, Yuriy Tymchuk <[email protected]> wrote: > > >> On 02 Dec 2013, at 17:42, Sean P. DeNigris <[email protected]> wrote: >> >> Uko2 wrote >>> It’s not about stability of pharo 3, it about concurrency... This thread >>> doesn’t seem to have any reason >> >> Nothing is wasted. I appreciate your ideas. I never thought of these >> benefits; I always took it for granted to run in one thread. > > Even if everything runs in one thread it doesn’t mean that you need to block > something. And I know that example with Nautilus or even with test runner may > be to hard. > > Let’s take moose for example. While it is importing a model everything > freezes. Is there a reason for that? I don’t see any. In my opinion the > problem is that we are not used to run non-instant operations in a separate > process, because I do a lot of mistakes like this too. > > uko > >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Responsible-development-tp4726686p4726763.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >
