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

List:       koffice-devel
Subject:    Re: Why is KSpread such a memory hog - analysis
From:       "\\\"shaheed r. haque\\\"" <srhaque () iee ! org>
Date:       2004-08-29 17:55:11
Message-ID: 1093802111.4132187f2928b () netmail ! pipex ! net
[Download RAW message or body]

On Sat, 28 Aug 2004 17:29:51 +0200, Thomas Zander <zander@kde.org> wrote:
> But going back and looking up stuff may just be the solution to this
> problem. (big leap in thought going on here..)
> what if:
> we read the XML stream and create low-overhead nodes for each node in the
> tree; just a parent, a childlist and a qstring for the name. Maybe another
> qstring for the NS.
> Next to that store the byteoffset in the stream in that node.
> 
> Provide a DOM interface on top of that and getting all the nodes-info
> becomes easy at that point. (slow, but doable).

This sounds a lot like a job for SAX? 
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]