Hello<br><br><div class="gmail_quote">2013/2/15 Sean P. DeNigris <span dir="ltr">&lt;<a href="mailto:sean@clipperadams.com" target="_blank">sean@clipperadams.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div id=":2nj">I don&#39;t know how efficient it would be, but how much text do we really<br>
layout at once? If it makes the code simpler and more beautiful, then it<br>
would be my starting point. Doing otherwise is premature optimization.</div></blockquote></div><br>I talk about amount of memory which required for text model where each character is separated &quot;big&quot; object.<br>

For example, I have small screen laptop and It contains nearly 8000 characters with single 9&#39;pt font which filled full screen. For big monitors I think it will be ~ 32000 characters. For my daily usage I have nearly 20 opened windows with some text (browser pages, articles). And I have nearly 50 saved latest closed windows at history pane. <br>

So such text model required significant amount of objects to cover my example. But I don&#39;t know is it really bad or not.<br><br>Actually I agree with your point: <br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">

If it makes the code simpler and more beautiful, then it<br>
would be my starting point<br></blockquote>And that&#39;s why I like what guys implemented. Good experiment.<br><br>In any case TxText is attempt to get clean object implementation of &quot;text stuff&quot; based on tests. So with little steps we can extend it and add new features. <br>

Now TxText can be used instead labels (not editable text morphs). Soon we will have cursor navigation, text selection and editing. I work on cursor now. (I mean visual part of TxText project).<br><br>Best regards,<br>Denis<br>

<br><br><br>