For now I'm sticking with putting annotations in meta-data. This has the
advantage of being able to use some of the metadocument.c code for
reading/writing the annotations, so there is less new code. Moreover, it
means one less record to search for via uids when opening a new record, etc.
On the viewer side, it makes a lot of sense. I made a slight change to the
format I posted previously: I inserted a 0xFFFFFFFF before the annotations
header, so an external utility can find the annotation without having to
know how many paragraphs are in a given record. I also added an extra
UInt32 reserved field for each annotation, which we can later use to specify
color or other attributes.
I propose (though don't volunteer to write) an external utility that takes a
metadocument, and can do several things:
(1) extract annotations and/or bookmarks to a specialized database
(2) merge in annotations and/or bookmarks from such a database
(3) convert annotations and/or bookmarks to memos
(4) delete annotations and/or bookmarks en masse from a metadocument
(5) beam the specialized database in (1) and (2)
This would allow for sharing of annotations.
Even if the annotations aren't in the metadata, such a utility would be
needed for merging annotations, if one wanted to do that. I don't think the
viewer should be capable of reading several annotation files on the
fly--that is too complicated to do while rendering.
Alex
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"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
