Smalltalk › Pharo › Pharo Smalltalk Developers

TxTextMorph based on new text model

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

24 messages Options

Sean P. DeNigris

Feb 14, 2013; 11:29pm

Re: TxTextMorph based on new text model

Administrator

5777 posts

Thanks again for tackling this! I'm definitely available to collaborate :)

Denis Kudriashov wrote

Do you think that presenting any letter with real object (not just
character) is sufficient for modern computers? I think not. Of course such
model significantly simplified all logic around text layout stuff. But I
think it is too expensive.

I don't know how efficient it would be, but how much text do we really layout at once? If it makes the code simpler and more beautiful, then it would be my starting point. Doing otherwise is premature optimization.

Denis Kudriashov wrote

Another thing which I always not agree is introduction scripting languages
inside smalltalk... [but] I like what they do inside rules. It is
really simple and understandable code.

Yes, I think a special scripting language would be way outside the bounds of Pharo, but the rules idea simplicity of that style could be great for us :)

Cheers,
Sean

Cheers,
Sean

Fernando olivero-2

Feb 14, 2013; 11:42pm

Re: TxTextMorph based on new text model

364 posts

In reply to this post by Denis Kudriashov

Hi, this is really interesting! To have a simpler text model and UI.

I recall Safara, in squeaksource. Lukas and a student worked on a nice text model. Worth checking it out.

Fernando

On Fri, Feb 15, 2013 at 12:29 AM, Sean P. DeNigris <[hidden email]> wrote:

Thanks again for tackling this! I'm definitely available to collaborate :)

Denis Kudriashov wrote
> Do you think that presenting any letter with real object (not just
> character) is sufficient for modern computers? I think not. Of course such
> model significantly simplified all logic around text layout stuff. But I
> think it is too expensive.

I don't know how efficient it would be, but how much text do we really
layout at once? If it makes the code simpler and more beautiful, then it
would be my starting point. Doing otherwise is premature optimization.

Denis Kudriashov wrote
> Another thing which I always not agree is introduction scripting languages
> inside smalltalk... [but] I like what they do inside rules. It is
> really simple and understandable code.

Yes, I think a special scripting language would be way outside the bounds of
Pharo, but the rules idea simplicity of that style could be great for us :)

Cheers,
Sean

--
View this message in context: http://forum.world.st/TxTextMorph-based-on-new-text-model-tp4663219p4669991.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

... [show rest of quote]

Denis Kudriashov

Feb 21, 2013; 5:18pm

Re: TxTextMorph based on new text model

2224 posts

2013/2/15 Fernando Olivero <[hidden email]>

I recall Safara, in squeaksource. Lukas and a student worked on a nice text model. Worth checking it out.

Thank's for link. I will look at code. Igor and Camillo, do you see this project?

Denis Kudriashov

Feb 21, 2013; 5:59pm

Re: TxTextMorph based on new text model

2224 posts

In reply to this post by Sean P. DeNigris

Hello

2013/2/15 Sean P. DeNigris <[hidden email]>

I don't know how efficient it would be, but how much text do we really
layout at once? If it makes the code simpler and more beautiful, then it
would be my starting point. Doing otherwise is premature optimization.

I talk about amount of memory which required for text model where each character is separated "big" object.
For example, I have small screen laptop and It contains nearly 8000 characters with single 9'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.
So such text model required significant amount of objects to cover my example. But I don't know is it really bad or not.

Actually I agree with your point:

If it makes the code simpler and more beautiful, then it
would be my starting point

And that's why I like what guys implemented. Good experiment.

In any case TxText is attempt to get clean object implementation of "text stuff" based on tests. So with little steps we can extend it and add new features.
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).

Best regards,
Denis