[Cuis-dev] An instance of Morph couldn't be moved by the halo's handle

[Szabolcs Komáromi]

My question is more hypothetical than practical. Is it a good idea to have a kind of morph that doesn't interact uniformly with other kinds of morphs? But maybe this is an irrelevant question and I should perceive the Morph class as an abstract class.

Regards,
Szabolcs

On Wed, Aug 16, 2023, at 22:07, Hilaire Fernandes via Cuis-dev wrote:
> For GUI (then layout), you don't want to use Morph because it does not 
> have location. The idea is to remove the unnecessary attributes
> 
> Le 16/08/2023 à 20:25, Szabolcs Komáromi a écrit :
> > For me Morph feels a little bit broken. Too simplified and feels like 
> > a special case. (But I certainly doesn't have a comprehensive overview 
> > of Morphic in Cuis.) E.g.: If I try to add a Morph instance inside a 
> > LayoutMorph I get an MNU because Morph doesn't implement layoutSpec. 
> > It brakes the uniformity of morphs.
> >
> >> a := Morph new.
> >> b := LayoutMorph newColumn.
> >> b addMorph: a.
> >> b openInWorld
> >
> > But I understand what was the rationale behind it.
> >
> > Regards,
> > Szabolcs
> 
> -- 
> GNU Dr. Geo
> http://drgeo.eu
> http://blog.drgeo.eu
> 
> -- 
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20230816/a17e3d91/attachment.htm>