You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It processes an annotation page.
Each anno is highlighting a box.
The app navigates the user around - like Ocean Liners.
Version 1
The annos target a 2D canvas, but they have a custom duration, before and after property (tbc). Appropriate for driving around someone else's canvas.
Version 2
The canvas has a duration, but the painting content is 2D, targeting the entire duration. The annos then just target their approriate t.
This app could achieve 1 by synthesising a new canvas with duration and modifying the annos, so it becomes the same as 2. In practice the raw data would probably some other JSON, not W3C annos, and the app wrapper would convert it to 2.
This demo draws out how we want CP to behave when rendering highlight annos.
If the canvas was 2D w,h and had highlighting annos, the default would be to show them all.
With duration, they only become visible in their time segments.
What does the developer need to do to get CP to show the anno boxes?
nothing?
wrap them each in DisplayAnnotation manually, so they become displayable styleable things?
This is not a full scale Ocean Liners display - the timing data doesn't need to be pulled out of IIIF (e.g., timed annos), it can just be in the code of the app, e.g., setTimeout for each new anno.
(from a Getty reqt)
This is a very lightweight app
It processes an annotation page.
Each anno is
highlighting
a box.The app navigates the user around - like Ocean Liners.
Version 1
The annos target a 2D canvas, but they have a custom duration, before and after property (tbc). Appropriate for driving around someone else's canvas.
Version 2
The canvas has a duration, but the
painting
content is 2D, targeting the entire duration. The annos then just target their approriatet
.This app could achieve 1 by synthesising a new canvas with duration and modifying the annos, so it becomes the same as 2. In practice the raw data would probably some other JSON, not W3C annos, and the app wrapper would convert it to 2.
This demo draws out how we want CP to behave when rendering highlight annos.
If the canvas was 2D w,h and had highlighting annos, the default would be to show them all.
With duration, they only become visible in their time segments.
What does the developer need to do to get CP to show the anno boxes?
See https://deploy-preview-50--iiif-canvas-panel.netlify.app/docs/examples/rendering-links#dealing-with-existing-linking-annotations and related discussion #33 (comment)
The text was updated successfully, but these errors were encountered: