From 78bbe38f04d123dc911b99d5c454b1b97494c469 Mon Sep 17 00:00:00 2001 From: Trip Kirkpatrick Date: Fri, 7 Mar 2025 13:45:18 -0500 Subject: [PATCH 1/2] =?UTF-8?q?Reworded=20Mirador=20caveat=20to=20look=20a?= =?UTF-8?q?head=20to=20Mirador=204=20when=20it=20won't=20have=20this=20pro?= =?UTF-8?q?blem=20=F0=9F=93=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- recipe/0033-choice/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipe/0033-choice/index.md b/recipe/0033-choice/index.md index e4ecb4f78..e1227fe7e 100644 --- a/recipe/0033-choice/index.md +++ b/recipe/0033-choice/index.md @@ -66,7 +66,7 @@ Clients that don't wish to offer a Choice UI should at least understand the cons In this example, we have a single Canvas with the `body.type` "Choice" containing two different photographs of the same painting: one using natural light and the other an x-ray image. -*Note: Currently, Mirador 3 only partially supports the layering of multiple images on a single Canvas. While previous iterations of Mirador processed the images upwards from the first painting annotation, Mirador 3 does this in reverse. This means that the first image in the "choice" body sits at the top of the "stack" in Mirador 3 rather than at the bottom.* +*Note: Mirador 4 fully supports this recipe, but Mirador 3 only partially supports the layering of multiple images on a single Canvas. While previous iterations of Mirador, as well as the new Mirador 4, process the images upwards from the first painting annotation, Mirador 3 does this in reverse. This means that the first image in the "choice" body sits at the top of the "stack" in Mirador 3 rather than at the bottom.* Credit: *John Dee performing an experiment before Queen Elizabeth I*. Oil painting by Henry Gillard Glindoni. Credit: Wellcome Collection. Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) From afc2fb4163e8266bed75f5f0a6febf32bd78e854 Mon Sep 17 00:00:00 2001 From: Trip Kirkpatrick Date: Fri, 21 Nov 2025 10:26:54 -0500 Subject: [PATCH 2/2] =?UTF-8?q?Updated=20note=20for=20Mirador=20v4=20?= =?UTF-8?q?=F0=9F=86=99?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- recipe/0036-composition-from-multiple-images/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipe/0036-composition-from-multiple-images/index.md b/recipe/0036-composition-from-multiple-images/index.md index 89275180e..96897f6f9 100644 --- a/recipe/0036-composition-from-multiple-images/index.md +++ b/recipe/0036-composition-from-multiple-images/index.md @@ -60,7 +60,7 @@ When composing a scene from multiple images, some images will require positionin A manifest with a single canvas that has two images painted on it. One is of the entire object, and one fills in a missing detail from the first image. Note that the `target` property for the second image (line 69) is appended with coordinates in order to position the the image on the appropriate region of the Canvas. -*Note: Currently, Mirador 3 only partially supports the layering of multiple images on a single Canvas and it is particularly noteworthy in this use case. While previous iterations of Mirador processed the images upwards from the first painting annotation, Mirador 3 does this in reverse. This means that the second image (the missing illustration detail) is hidden behind the image of the full folio and the user cannot view the reconstructed scene.* +*Note: Mirador 4 fully supports this recipe, but Mirador 3 only partially supports the layering of multiple images on a single Canvas. While previous iterations of Mirador, as well as the new Mirador 4, process the images upwards from the first painting annotation, Mirador 3 does this in reverse. This means that the second image (the missing illustration detail) is hidden behind the image of the full folio in Mirador 3 and the user cannot view the reconstructed scene.* {% include manifest_links.html viewers="Mirador, Annona, Theseus, TIFY" manifest="manifest.json" %}