On Mon, 23 Jun 2003, Adam McDaniel wrote:
> How about this. Instead of storing the 'yoffset' for the bookmark,
> store a character offset based upon the DB itself.
A character offset is slow to seek to. (Try to seek to a search
string.) That could be improved, now that I have the faster page loading
done. (Currently the faster code isn't used for seeking to the search
string, but it could be.) But it still would be a little slow.
I was thinking of storing BOTH the yoffset AND the character offset. At
least for the history, this would be nice. But there should be some way
of optimizing. I just probably shouldn't be putting much more time into
this.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
