<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Hilaire, On 3/28/2025 12:51 PM, Hilaire Fernandes via Cuis-dev wrote: <blockquote cite="mid:cf6a53cf-1781-4855-b49a-e58149872522@free.fr" type="cite"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi folks, This class urgently needs a minimum survival comments . There are many aspects of this class which are obscure. I hope Juan is not the only person knowing about it and that other people can comment it. Current comment is: "The main morph for text editors" Information needed on : <ul> <li>#changed: complete list and meaning of symbol</li> <li>what methods do? </li> <li>what the inner morph does?</li> <li>what </li> </ul> We are trying to document it in the booklet and it is painful and behavior is strange or unknown. If you have knowledge, share it there then we can elaborate a useful comment. Thanks <pre class="moz-signature" cols="72">-- <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo">http://mamot.fr/@drgeo</a></pre> </blockquote> Yes. True. I think that the whole PluggableMorph hierarchy needs better class comments. All these classes have a model, and they are "pluggable" in the sense that they don't know mucho about their model. This makes it possible to use them in different situations. For instance, TextModelMorph. The name tries to tell that this is a morph intended to be used with a TextModel as a model. Compare, for instance, with EntryFieldMorph, that can be used without a model at all. I think that the internals of TextModelMorph / InnerTextMorph are not really important. What matters is how they interact with a TextModel. See that a basic TextModel only holds a Text and the undo/redo stuff. But a PluggableTextModel is more powerful. It can interact with some application level object that stores the text, and accepts the new contents. For instance, the textProvider of a PluggableTextModel may be a FileList (to view and edit text files) or a Browser (to view and edit methods). I hope this quick description makes sense. A lot more is needed, no doubt. Cheers, <pre class="moz-signature" cols="72">-- Juan Vuletich cuis.st github.com/jvuletich researchgate.net/profile/Juan-Vuletich independent.academia.edu/JuanVuletich patents.justia.com/inventor/juan-manuel-vuletich linkedin.com/in/juan-vuletich-75611b3 twitter.com/JuanVuletich</pre> </body> </html>