On 17 May 2012 13:44, St�phane Ducasse <
stephane.ducasse@inria.fr> wrote:
>
> On May 16, 2012, at 10:59 PM, Guillermo Polito wrote:
>
>>
>> On Wed, May 16, 2012 at 8:59 PM, St�phane Ducasse <
stephane.ducasse@inria.fr> wrote:
>> I do not really like the class idea.
>>
>> why not? �Maybe it does not apply for every process, but for some of them.
>
> Because I'm not sure that I like having one class per object.
>
>> Morphic UI process could belong to MorphicUIManager, but, does the finalization process belong to weak array? why not to weak registry or weak ordered collection then? :S
>>
>> May be having a convention + a pragma for the methods is good.
>>
>> Stef
>>
>> On May 16, 2012, at 3:27 PM, Guillermo Polito 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
>>
>>
>>
>
>