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
I recommend changing the order in which presentation hints are, well, presented... since this could facilitate understanding, in my opinion:
continuous (-> high level, linked to story type)
fit (-> technically the first operation applied to a given resource: "try to make it fit in the viewport according to its stated fit")
overflow (-> "once the resource fits in the viewport, if parts of it lie outside the viewport, decide whether those parts should be made accessible - through scroll or pagination - or not")
clipped (-> "you know what, actually clip (or not) all resource parts outside the viewport, whatever the overflow")
spread (-> "allow a double-page reading mode")
orientation (-> "block reading in only one orientation or not")
Going one step further, I recommend that the properties of a Link Object that are relevant to the divina case be presented in an order consistent with the former:
fit (overrides the story fit)
clipped (overrides the story clipped)
page (whether the resource is a left, center or right page in a double page)
The text was updated successfully, but these errors were encountered:
I recommend changing the order in which presentation hints are, well, presented... since this could facilitate understanding, in my opinion:
Going one step further, I recommend that the properties of a Link Object that are relevant to the divina case be presented in an order consistent with the former:
The text was updated successfully, but these errors were encountered: