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
...but CP site shouldn't be the go-to place for Atlas docs. Just enough for context.
Getty comments:
For a bookviewer:
it would be useful to have an example with pagination... i.e. not just rendering facing pages, but rendering how the next set of pages (and pagination) are envisioned to be managed
It would be useful to have an example of a gallery view of pages in a bookviewer
It looks like for constructing the bookviewer, the documentation outlines nesting canvas-panel components inside an atlas-viewer component, but there’s not a whole lot of documentation in the Atlas components section or at the link to github repo: https://github.com/atlas-viewer/atlas
The text was updated successfully, but these errors were encountered:
(NB these comments are perhaps out of scope purely for Canvas Panel because they are about its use in a wider context)
Do we consider the Florentine Codex reader an example that meets these requirements?
For Atlas, we need to augment this a bit:
https://iiif-canvas-panel.netlify.app/docs/components/atlas
...but CP site shouldn't be the go-to place for Atlas docs. Just enough for context.
Getty comments:
For a bookviewer:
it would be useful to have an example with pagination... i.e. not just rendering facing pages, but rendering how the next set of pages (and pagination) are envisioned to be managed
It would be useful to have an example of a gallery view of pages in a bookviewer
It looks like for constructing the bookviewer, the documentation outlines nesting canvas-panel components inside an atlas-viewer component, but there’s not a whole lot of documentation in the Atlas components section or at the link to github repo: https://github.com/atlas-viewer/atlas
The text was updated successfully, but these errors were encountered: