On Wed, May 16, 2012 at 3:27 PM, Guillermo Polito <[email protected]> wrote: > I'm playing with the process initialization for the bootstrap, and some > things come to my mind. > > There are some classes that startup processes on the class side initialize, > like > > WeakArray -> Finalization process > Delay -> Timer event loop > > What it is not clear to me is if those processes should be installed when > the class is initialized, or when it is startupped for the first time. > Also, I can't stop thinking that the processes in the image are all spread > and not clear. If I want to know where the processes are defined, it's kind > of a mess. > > Is having specialized objects for our processes undesired by some reason I > can't see? I'd like to have objects like > > MorphicUIProcess > FinalizationProcess > TimeEventProcess > ... > and so on > > Guille
I'm pretty sure that the there is no real binding between the class where the processes are created and the processes themself. The Pharo Kernel terminates all but this processes: InputEventFetcher default instVarNamed: #fetcherProcess. Processor activeProcess. WeakArray runningFinalizationProcess. Processor backgroundProcess. ...and it restarts this process: Delay startTimerEventLoop. I think that to have separate classes for the basic system processes is a good idea. -- Pavel
