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.
1. Support of large files ( >> 100mb)
2. Support of large pieces of text located in memory
3. Allow developers to embed visual elements (pictures, interactive
elements, custom elements)
4. Support of more sophisticated layouts rather than line-based. For
example columns.
5. Line breaking
6. Text wrapping
7. Hyphens
8. 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?
