Is there no way Igor can finish this up?

Not that I know.
I did not get why Igor went totally off like that.

Phil


Le 23 oct. 2016 12:19, "stepharo" <steph...@free.fr <mailto:steph...@free.fr>> a écrit :


        Hi Stef,

        We are not throwing away anything. The goal is not to produce
        a new model, the goal is to find one that matches the
        requirements.

    Don't play with words.

        We already learnt a lot from TxText, but it has limitations in
        how to deal with things that are not only text.

    I can imagine.

        We have no intention of producing an unfinished text model :).

    Me neither with igor and txText yet life decided otherwise. You
    see I spent at 10 months of salary on txText.

          This is a critical component for us. Please let us work for
        a couple of months and we get back with news.

        Cheers,
        Doru


            On Oct 22, 2016, at 8:31 PM, stepharo <steph...@free.fr
            <mailto:steph...@free.fr>> wrote:

            Hi aliaksei

            I thought that you were just changing the internal
            representation of txText to use Ropes
            and building on top of / improving txText
            I did not think that you were throwing away all the work
            igor did. Because he spent a lot of time

            designing the text model and making it is scalable - and
            now I read that apparently it was not scalable enough.
            I'm wondering what will happen if suddenly you disappear:
            we will get two unfinished textmodel
            and use an old one? When do you think that you will have a
            working usable by other for real text model?
            Stef

            Le 22/10/16 à 12:29, Aliaksei Syrel a écrit :

                As Doru already mentioned text editor is an important
                part of the tools. There are some requirements a text
                editor should fulfil.

                        • Support of large files ( >> 100mb)
                        • Support of large pieces of text located in
                memory
                        • Allow developers to embed visual elements
                (pictures, interactive elements, custom elements)
                        • Support of more sophisticated layouts rather
                than line-based. For example columns.
                        • Line breaking
                        • Text wrapping
                        • Hyphens
                        • Should be fast
                Tests show that TxText model is very nice for basic
                cases, works well for "normal" use.
                However, when it comes to extreme cases linked list of
                spans just fails, while rope shows great performance -
                and it also scales.

                Cheers,
                Alex

                On 19 October 2016 at 23:51, Denis Kudriashov
                <dionisi...@gmail.com <mailto:dionisi...@gmail.com>>
                wrote:

                2016-10-19 18:06 GMT+02:00 Aliaksei Syrel
                <alex.sy...@gmail.com <mailto:alex.sy...@gmail.com>>:
                  - Added initial text support, for instance rendering
                and high precision measurement.

                I look at code and it seems you implemented another
                one new text model? Why you not use TxText?

        --
        www.tudorgirba.com <http://www.tudorgirba.com>
        www.feenk.com <http://www.feenk.com>

        "Some battles are better lost than fought."









Reply via email to