<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi Juan, The WidgetMorph hierarchy is a great idea. Newcomer with programming background will be more comfortable to have two hierarchies: one for more traditional GUI and another one for original and creative view. I agree with you StringMorph is a strange name, LabelMorph is more aligned to the convention of the world of GUI, and it is a widely used in GUI definition. The world Label is meaningful in many human languages, this is another advantage aginst String, a low level term in cs. Its unique added value is its name match the name of the associated literal it displays on screen. If it is not too much trouble, I would vote for the name change. Hilaire <div class="moz-cite-prefix">Le 13/10/2020 à 16:43, Juan Vuletich a écrit : </div> <blockquote type="cite" cite="mid:5F85BD1C.3010205@jvuletich.org">In this way, all Widget morphs will be in the WidgetMorph hierarchy, improving consistency and making it easier to explain and remember. - RectangleLikeMorph and BorderedRectMorph might get deleted. PasteUpMorph, HandMorph, HaloMorph, HaloHandleMorph and EllipseMorph could be subclasses of Morph. This will need some rework of their internals. - Additionally, I want to rename StringMorph as LabelMorph, as 'label' is less ambiguous, and is how a read-only string widget is usually called. </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre> </body> </html>