<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"/></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Mark,<div><br/></div><div>Thanks for your suggestions. I like your class comment. IMO it could be taken as is. If it should be shorter here is what I suggest based on your text:</div><div><br/></div><div><div><font face="monospace">A TextModelMorph enables users to view and edit text. Its main features are:</font></div><div><font face="monospace">- using either a TextModel or TextProvider to hold the text being edited<br/>- styling and text wrapping (provided by InnerTextMorph)<br/>- scrolling with scrollbars (provided by superclass PluggableScrollPane)<br/><br/>There are two approaches for creating instances. One approach is to hold the text value in a TextModel object. The class methods withModel: and withText: support this. The other approach is to hold the text value in a TextProvider. The class methods that begin with textProvider: support this. For examples, see the method comments in those class methods.<br/><br/>A border is displayed when it has focus.<br/><br/>By default, words that would extend past the right side wrap to the next line. To prevent wrapping, send an instance #wrapFlag: with an argument of false.<br/><br/>To change the size, send an instance #morphExtent: with a Point argument. The size should include space for scroll bars if they may be needed. Setting the height to zero causes it to actually be set to the height required for a single line in the current font.</font><br/><font face="monospace"><br/>Related classes include TextModel, PluggableTextModel, TextProvider, PluggableScrollPane, and InnerTextMorph.<br/></font></div><div><br/></div><div>Cheers</div><div>Bernhard</div><div><br/></div><div><br/><blockquote type="cite"><div>Am 06.04.2025 um 14:27 schrieb Mark Volkmann via Cuis-dev <cuis-dev@lists.cuis.st>:</div><br class="Apple-interchange-newline"/><div><div dir="ltr">I'd love to get suggestions from others that share how they would reword this, including what they would cut. I just included everything I felt was important to know when I started learning about this class.</div><br/><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Apr 5, 2025 at 1:15 AM Hilaire Fernandes via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:<br/></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><u></u>
<div bgcolor="#FFFFFF"><p><font size="4">Thanks Mark!<br/>
</font></p><p><font size="4">There are important tips in your suggested
comment.</font></p><p><font size="4">It seems a bit too verbose to me, though. It reads
as book documentation and not comment, which may want to be more
concise with a more telegraphic wording. </font></p><p><font size="4">Other may have different opinion though, I hope
they can share it. <br/>
</font></p>
<pre cols="72">--
<a href="http://mamot.fr/@drgeo" target="_blank">http://mamot.fr/@drgeo</a></pre>
</div>
-- <br/>
Cuis-dev mailing list<br/>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br/>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br/>
</blockquote></div><div><br clear="all"/></div><div><br/></div><span class="gmail_signature_prefix">-- </span><br/><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div><font face="arial, helvetica, sans-serif">R. Mark Volkmann</font></div><div><span style="font-size:12.8px"><font face="arial, helvetica, sans-serif">Object Computing, Inc.</font></span></div></div></div></div></div></div></div></div>
</div></blockquote></div><br/></div></body></html>