2016-04-06 18:00 GMT+02:00 Igor Stasenko <siguctua@gmail.com>:


On 6 April 2016 at 18:34, Nicolai Hess <nicolaihess@gmail.com> wrote:


Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <siguctua@gmail.com>:
>
> 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.