Node Indexing
The node indexing facility is used to create a list of internal nodes withina document (file) without scanning the whole document. Thus the opening of a document speeds up significant.

If a document is open the first time, the datatype scans the whole documentand creates a list of internal nodes. With node indexing turned on, the datatype saves all needed information, so it can read these informations by a later opening of the document. The hypertext datatype supports now two ways of saving these informations :

1. Saving the information in the tooltypes of the appropriate icon. (old save method)
   
2. Saving the information in a separate file in a configured directory. (new save method)

But the information isn't correct if the document meanwhile changed. In this situation the HyperText datatype checks the date stamps for the icon and the real document and if the document is newer it scans the document as it is opened the first time. So node indexing is absolutly transparent for document writers, if you have a working realtime clock.

For example the gcc.guide (about 1.2 MB large) took about 9 secs for opening without node indexing on my system. With node indexing it tooks under 1 sec.

See Also
Configuration