ISSUE-302: A Saga of JS driven IIIF Interactions #303
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not yet there but advancing. Still very experimental but i think i got this
DiegoPino
added
enhancement
Very good Diego
But..the new IIIF Geo specs are strange. Means for our (my Math capabilities) i can only warp via CSS/Leaflet the topleft/topright/bottomleft and bottomright of an annotation. The Specs define one Lat/long v/s one X,Y point, so instead of saving a full Polygon feature in the annotation body i have to go point by point, and since x,Y are relative to the fragmens (the target) i have to do more and more maths. C'mon!!
Clip-path parsed from the W3C annotation polygon
…anifests Not working yet But if i don't push I will die (dies)
Still, need to check of course, but now the hard part. JS!
Because our markers are extra grouped here i might have to do some empiric tests (build a view/etc) to make sure all is OK (maybe tomorrow @alliomeria ?)
Ok, ok, ok. Tiredddd
Lot's of promises and async here so was a bit harder. But basically with this OSD can read any Service based (/info.json) manifests and thus annotated, which of course includes PDFs but also CreativeWorkSeries, books, you name it!
Not ready yet, we need to act on these new options
I might have gotten this wrong so another pull might follow
But i will keep a few, they are fun! Like a data logger of sorts of my late night work
Everyone talking to each other One downside of the manifest/canvas ado interaction is that on the caller i need to calculate the canvas id which uses the uuid ...
For an ADO change to be triggered it needs:
"sbf:ado:change": nid
for an view change the JSON-LD or the GEOJSON needs
'sbf:ado:view:change': nid or any exposed/relationship value one wants to pass/view receiving accepts.
For a canvas change it needs (Mirador does nothing, it will trigger the canvas change on change) but maps needs
"sbf:ado:canvas:change": {
"canvasid": the id of the canvas,
"manifestid": the id of the manifest
}
This is a bit tooo precise for my taste? mmmm
Wonder if Mirador should also react to ADO change? And i do the "find the canvas that contains the actual ID i'm searching for? mmmm
Probably
If we want reaction we add `sbf:ado:change:react`, if we want to trigger a reaction somewhere else we use `sbf:ado:change` Also we avoid self reactions to avoid looops
We need settings here ?
|
@esmero/archipelago-core. Merging this, has been in production for 10 days without issues. There is still work todo. e.g add the same override options via JSON to Mirador, make OSD react to Events, etc. But this was becoming too large already |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #302. Starting here with Mirador and moving into each IIIF driven/enabled (or able to react) Viewer we provide.
WIP, will keep adding commits and comments and will update this once all is done.