TxText model

On 6 April 2016 at 11:36, Nicolai Hess <[hidden email]> wrote:

Thanks Igor.

Maybe some more Info? (I don't have much experience with this and don't fully understand what is missing).

 

1. No support for vector graphics

I know some parts of Athens (with Cairo font renderer and how it is used in TxText) but at the moment

rendering a TextMorph in Athens works:
Morph comment asText asMorph openInSceneView

Sorry, missed to reply to that important point.

It works because one good soul spent effort and helped me to finish  implementation of a wrapper for Morph, to be able to render any morph into Form, and then render Form

on Athens surface.

So, that is why it 'works' :)

--

Best regards,
Igor Stasenko.

2016-04-06 10:56 GMT+02:00 Igor Stasenko <[hidden email]>:

On 6 April 2016 at 11:36, Nicolai Hess <[hidden email]> wrote:

Thanks Igor.

Maybe some more Info? (I don't have much experience with this and don't fully understand what is missing).

 

1. No support for vector graphics

I know some parts of Athens (with Cairo font renderer and how it is used in TxText) but at the moment

rendering a TextMorph in Athens works:
Morph comment asText asMorph openInSceneView

Sorry, missed to reply to that important point.

It works because one good soul spent effort and helped me to finish  implementation of a wrapper for Morph, to be able to render any morph into Form, and then render Form

on Athens surface.

Nah, actually it works a bit different. Many (Form)Canvas methods are reimplemented on Athens API. But yes, I used some hacks as well.

 

So, that is why it 'works' :)

--

Best regards,
Igor Stasenko.

Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <[hidden email]>:
>
> btw,
>
> if you wanna feel a difference, why we wanted vector based rendering, by yourself, open:
>
> Morph comment asText asMorph openInSceneView
>
> and then
>
> | sceneView view |
> sceneView := AthensSceneView new.
> view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400.
>
> sceneView scene: view.
> sceneView openInWindow 
>
>
> and try zooming it in and out with mouse wheel.
>
>

I know it's limitation. My point was, that it is not impossible, or depends an the model Text vs. TxModel, alone.

On 6 April 2016 at 18:34, Nicolai Hess <[hidden email]> wrote:

Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <[hidden email]>:
>
> btw,
>
> if you wanna feel a difference, why we wanted vector based rendering, by yourself, open:
>
> Morph comment asText asMorph openInSceneView
>
> and then
>
> | sceneView view |
> sceneView := AthensSceneView new.
> view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400.
>
> sceneView scene: view.
> sceneView openInWindow 
>
>
> and try zooming it in and out with mouse wheel.
>
>

I know it's limitation. My point was, that it is not impossible, or depends an the model Text vs. TxModel, alone.

Of course it doesn't depends on either of those. But it wasn't an answer concerning model, but you question why i had to abandon idea to keep using DisplayScanner & friends. 

--

Best regards,
Igor Stasenko.

2016-04-06 18:00 GMT+02:00 Igor Stasenko <[hidden email]>:

On 6 April 2016 at 18:34, Nicolai Hess <[hidden email]> wrote:

Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <[hidden email]>:
>
> btw,
>
> if you wanna feel a difference, why we wanted vector based rendering, by yourself, open:
>
> Morph comment asText asMorph openInSceneView
>
> and then
>
> | sceneView view |
> sceneView := AthensSceneView new.
> view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400.
>
> sceneView scene: view.
> sceneView openInWindow 
>
>
> and try zooming it in and out with mouse wheel.
>
>

I know it's limitation. My point was, that it is not impossible, or depends an the model Text vs. TxModel, alone.

Of course it doesn't depends on either of those. But it wasn't an answer concerning model, but you question why i had to abandon idea to keep using DisplayScanner & friends. 

Sure, but as you talked about limitiations solved by TxText, I thought about limitation for building editor/tools around Text or TxText.

I see that you had rendering vector based graphics with TxText and Athens.

What I want to see, is a Text-Tool framework for building custom editors or easily add features (code tools or tools for other kinds of text).

Rubric comes close, it has some good features for  text decorations.

Twisty looks promisinig too, I like that it is build on similar classes like TxText but looks more finished.

(As it is based on TxText (or a fork) maybe it isn't that difficult to add rendering on athens ?)

 

--

Best regards,
Igor Stasenko.

Ok. Call me stupid but in Pharo I don't see how to do that easily.

Phil

On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont <[hidden email]> wrote:

On 06-04-16 11:13, [hidden email] wrote:

Another pain is the styling of text where the only styler we have is the SHSt80Styler (class name out of my mind, need to check) and that's a huge pain to support other stylings.

Styling with different stylers worked in TextMorph. In Squeak it is easy
to add styling for a different language in the class browser. Levente did
that for PostgreSQLv3.

Stephan

(As it is based on TxText (or a fork) maybe it isn't that difficult to add rendering on athens ?)

The only thing required for styling is to specify the attributes for the runs associated with the text.

A simple example:

 

| text attributes oldRuns clr|

 

text := (String loremIpsum: 1234) asText.

 

attributes := Array new: text size.

 

clr := TextColor color: Color random.

 

1 to: text size do: [ :index |

               attributes at: index put: {

                              clr.

                              TextFontChange font2   

               }.

              

               (text at: index) isSeparator ifTrue: [ clr := TextColor color: Color random ]

].

 

text runs: (RunArray newFrom: attributes).

 

text

 

 

Best regards,

Henrik

 

From: Pharo-dev [mailto:[hidden email]] On Behalf Of Nicolai Hess
Sent: Wednesday, April 6, 2016 8:23 PM
To: Pharo Development List <[hidden email]>
Subject: Re: [Pharo-dev] TxText model

 

 

 

2016-04-06 18:11 GMT+02:00 [hidden email] <[hidden email]>:

Ok. Call me stupid but in Pharo I don't see how to do that easily.

 

Phil

 

At least for Rubric, it can not be that difficult. I saw a GT-Inspector with a XML-styer

 

 

On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont <[hidden email]> wrote:

On 06-04-16 11:13, [hidden email] wrote:

Another pain is the styling of text where the only styler we have is the SHSt80Styler (class name out of my mind, need to check) and that's a huge pain to support other stylings.

Styling with different stylers worked in TextMorph. In Squeak it is easy
to add styling for a different language in the class browser. Levente did
that for PostgreSQLv3.

Stephan