integrate tify?

[eroux]

The mobile-friendly tify iiif image viewer recently added collection viewing (demo)

Perhaps it's something we might want to integrate in the app, or perhaps implement in the existing iframe

[subsystem7]

This looks very promising!On Nov 3, 2022, at 5:22 AM, Elie Roux @.***> wrote: The mobile-friendly tify iiif image viewer recently added collection viewing (demo) Perhaps it's something we might want to integrate in the app, or perhaps implement in the existing iframe

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[t11r]

Hi there, maintainer of TIFY here. Glad you are considering using TIFY, as I used some of the manifests from BUDA for testing, which are among the largest collections that I could find. Should there be any issues or recommendations concerning your use case, please let us know.

[eroux]

@t11r thanks a lot for your message, this is really generous of yours! I've left a few comments in the issue tracker, generally speaking I don't think there's anything blocking but we'll test further and will report any issue we spot

[eroux]

@ngawangtrinley what do you think? It seems to have a lot of potential, can you give it a try? If we adopt it we'll have to provide Tibetan and Chinese translations but there aren't a lot of string so it should be fast (see here)

@berger-n can you think of other features we added to mirador2 that should be added to tify? There's the reading view but on mobile it's probably not that useful

[ngawangtrinley]

Tify looks really good! The localization won't be an issue, but we should keep the reading view!

The most important will be the basic book reading experience. BDRC Mobile users really like the "reading view" with the infinite scrolling which is well suited for the pecha layout and which can be scrolled by swiping anywhere on the screen.

The "page view" with the option of zooming for details seems to be the core feature of most IIIF viewers. It is not that important for our readers as we use the viewer as an e-reader.

When using the app as an e-reader, users expect behaviors similar to an epub reader where you can tap on either side to flip to the next page. The page view feature mostly gets in the way of that reading experience. Users want to be able to pinch and zoom in an out while still being able to navigate the book by swiping anywhere on the screen (or by tapping either half of the screen). The "page view" feature generally gets in the way of the reading experience, since the basic page navigation requires more effort. I like the bottom corner navigation areas but they aren't as seemless as the average epub reader. I guess BDRC's usecase is quite niche since we don't have good etexts/epubs for most of our collection -- yet.

Here's an illustration to showcase why vertical scrolling works better for pecha format. My understanding is that it mainly has to do with the length of lines.

[t11r]

Sorry to dash your hopes, but while I admit this would be a very nice feature, I don’t see it happening anytime soon.