On Tue, 24 Jun 2003, Jewett, Jim J wrote:
> Am I understanding this correctly? In order to jump to
> #section5 which is 87% of the way through a document,
> you first have to pretend you're rendering every single
> line above it, to until the YOffset finally matches.
The old code did that when s
Alexander R. Pruss wrote:
> Well, anybody who wants to benchmark whether performance
> was degraded can do so. My own feeling is that the amount of
> degredation is going to be miniscule.
OK; I thought you were saying that it was noticeable in your
tests even without benchmarking.
> Moreover,
On Tue, 24 Jun 2003, masakazu wrote:
> I've just started to implement conversion functions between the
> position on
> screen and the position in the context. Your work is very much helpful
> for me.
> I will stop my job for a while to wait you finish.
I suggest you (or I or whoever) use the Sea
Hi,
I just had an idea. What if the parsers simply insert a paragraph with 0
spacing whenever a is encountered. Visually, this should give the
same result as inserting a newline function code, but the performance
should be (much) better.
I see two issues:
1) The document becomes larger due to
On 2003.Jun.24, at 12:39 AM, Alexander R. Pruss wrote:
Well, I've implemented and committed something that eliminates some of
the
duplication of effort between WriteLine() and GetLineMetrics(). Under
POSE/NR70 it speeds up my benchmark page from 26 sec to 10 sec. On my
NX70, it sped up the sam
