Issue 3266 in pharo: Clean TextEditor

Hi Stef,

Stéphane Ducasse wrote:
>>> - clean again all the MVC dependencies....
>>>  
>>>      
>
> FillInTheBlank? PopUpMenu?
>  

Those might be not pretty, and I agree they can be replaced by something
better, but they are not MVC dependencies.

>  
>> Well, that doesn't stop Mariano from fighting the deepest internals of the VM... Developing any needed know-how in the Pharo community will ensure that Pharo will survive any technical difficulties that might arise in any part of the system.
>>    
>
> yes this is the idea.
> And we should do it but again my plate is full

That's ok. But you are the leader of the community. When you say:

"I do not think that we can build something on simpleMorphic, what we
can do is look at the kernel and see how the changes can be applied to
Morphic",

 it really means that it should better not be done. It means "I think it
can't be done, don't waste your time".

If, instead of that, you say "I can't help, but feel free to go ahead",
the reaction of the community will be completely different.

Cheers,
Juan Vuletich

Indeed. I mean
        I can't help, but feel free to go ahead

Stef

IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
(i mean get rid that 'color' thing in base class)  :)


On 24 November 2010 16:49, Stéphane Ducasse <[hidden email]> wrote:


--
Best regards,
Igor Stasenko AKA sig.

Stéphane Ducasse wrote:
> Indeed. I mean
> I can't help, but feel free to go ahead
>
> Stef
>
>  
Great! Thanks for the clarification.

Cheers,
Juan Vuletich

Igor Stasenko wrote:
> IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
> (i mean get rid that 'color' thing in base class)  :)
>
>  

Yep. I fully agree.

Cheers,
Juan Vuletich

On 25 November 2010 03:45, Juan Vuletich <[hidden email]> wrote:
> Igor Stasenko wrote:
>>
>> IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
>> (i mean get rid that 'color' thing in base class)  :)
>>
>>
>
> Yep. I fully agree.
>
I think, for things like Morphic, where there are dozens of various
properties expected
to be in basic morph class, we should use dictionaries, backed up by
clever VM semantics.
I cannot stop thinking about extending object format to allow a
dynamic number of slots per object,
like in self or javascript.


> Cheers,
> Juan Vuletich
>
>



--
Best regards,
Igor Stasenko AKA sig.

Igor Stasenko wrote:
> I think, for things like Morphic, where there are dozens of various
> properties expected
> to be in basic morph class, we should use dictionaries, backed up by
> clever VM semantics.
> I cannot stop thinking about extending object format to allow a
> dynamic number of slots per object,
> like in self or javascript.
>
>  

That sounds interesting, and I'm sure there are many applications that
could benefit from it.

Cheers,
Juan Vuletich

this is just for state. You have traits for methods.
For me the way to go is first clean the classbuilder, have first class instance variables,
what you want is just
                hashSubclass:
                instead of variableSubclass:
Stef

Now I will see who will port/rewrite what we have on top of a cleaned SimpleMorphic.