Changes between Version 12 and Version 13 of AnnotationDisplay


Ignore:
Timestamp:
02/13/08 14:26:38 (9 years ago)
Author:
pichota
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnnotationDisplay

    v12 v13  
    5454=== Typical Use Case === 
    5555 
    56 Upon page loading the application specific function `initAnnotationDisplay()` and the general `initAnnotationDisplayGeneric()` create the specified filters, setup the environment and retrieve annotations depending on the filter values stored in the cookie. The also application dependent `retrieveAnnotations()` creates the query string that is transmitted as an AJAX request to the servlet by `retrieveAnnotationsGeneric()`. Upon the receive event the previously existing state is deleted in `unprocessAnnotations()` and recreated during `processAnnotations()`. Global structures are initialized before each received annotation is processed individually in `extractAnnotationInformation()` which is the core of the algorithm. All fragments belonging to an annotation were derived in a preprocessing step and are now assigned to the annotation objects. The sorted fragments are then used to augment the paragraphs, i.e. generate an icon, set the read status and make them react on mouse over / out events. All information ever needed for future events have been gathered and are directly available through `annotationsByUri`, `annotationsByParagraph`, `orderedAnnotationUris` in the first place and via `annotation.fragments`, `annotation.paragraphs`, the paragraphs themselves in the second place. 
     56Upon page loading the application specific function `initAnnotationDisplay()` and the general `initAnnotationDisplayGeneric()` create the specified filters, populate them via AJAX request, setup the environment and retrieve annotations depending on the filter values stored in the cookie. The also application dependent `retrieveAnnotations()` creates the query string that is transmitted as an AJAX request to the servlet by `retrieveAnnotationsGeneric()`. Upon the receive event the previously existing state is deleted in `unprocessAnnotations()` and recreated during `processAnnotations()`. Global structures are initialized before each received annotation is processed individually in `extractAnnotationInformation()` which is the core of the algorithm. All fragments belonging to an annotation were derived in a preprocessing step and are now assigned to the annotation objects. The sorted fragments are then used to augment the paragraphs, i.e. generate an icon, set the read status and make them react on mouse over / out events. All information ever needed for future events have been gathered and are directly available through `annotationsByUri`, `annotationsByParagraph`, `orderedAnnotationUris` in the first place and via `annotation.fragments`, `annotation.paragraphs`, the paragraphs themselves in the second place. 
    5757 
    5858The above applies to the actions performed when a filter value is changed, too.