[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    KoTextParag data structure
From:       "Sunny Sun" <sunnyawake () gmail ! com>
Date:       2007-01-20 3:06:15
Message-ID: e2c32b3f0701191906v6fcf5bev88f39b210879abec () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


i'm a java programmer from China, not familiar with qt, so maybe the
following questing seems stupid.

when i browse KoText source, i find KoTextParag uses KoTextString as text
data, which uses Q3MemArray<KoTextStringChar>. the KoTextStringChar is a
wrapper around QChar, so every char in a paragraph is an object. i think
this is the case for all apps that use KoText lib.

is this kind of a big waste and terribely ineffient? since koffice 2.0 just
started, why don't we redesign this core part?

(in fact we're developing an office using java, EIOffice. at present it is
not perfect, but we are very careful of very byte usage when designing our
data structure.)

[Attachment #5 (text/html)]

i&#39;m a java programmer from China, not familiar with qt, so maybe the following \
questing seems stupid.<br><br>when i browse KoText source, i find KoTextParag uses \
KoTextString as text data, which uses Q3MemArray&lt;KoTextStringChar&gt;. the \
KoTextStringChar is a wrapper around QChar, so every char in a paragraph is an \
object. i think this is the case for all apps that use KoText lib. <br><br>is this \
kind of a big waste and terribely ineffient? since koffice 2.0 just started, why \
don&#39;t we redesign this core part? <br><br>(in fact we&#39;re developing an office \
using java, EIOffice. at present it is not perfect, but we are very careful of very \
byte usage when designing our data structure.) <br><br>



_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]