Feature #1499
Mis à jour par Serge Heiden il y a environ 10 ans
h3. Diagnostic A
Since import modules now produce text editions which always display metadata information at the beginning of each text, it is easy now to understand when we are at the beginning of a new text. But to read the next text after the end of the current one, one has to use the 'next text' button which is not practical for corpora made of small texts.
Furthermore, if we consider a corpus as a sequence of texts - which is always the case (at least by construction/implementation, even if no chronological data is available) - texts reading navigation should modelize/help natural navigation from the last page of a text to the first of the next one.
h3. Solution A
Change the behavior of the 'next page' button: when the end of text is reached, display the first page of the next text if available.
Add a symetric behavior for 'previous page': when the beginning of text is reached, display the last page of the previous text if available.
h3. Diagnostic B
Current text edition navigation design uses 3 types of commands:
* next page, >
* end of text, >|
* next text, >>
It would be more intuitive for navigation (easier to learn) to balance behaviors between text pages navigation and texts navigation by adding navigation commands to 'last text' (aka end of corpus).
h3. Solution B
Add two additional commands and buttons to the Edition editor navigation toolbar:
* First text (go to first page of first text), |<<
* Last text (go to first page of last text), >>|
MD: both solutions implemented
MD: implemented also in the SynopticEditor
SH: we also need to implement this in the Portal edition
Since import modules now produce text editions which always display metadata information at the beginning of each text, it is easy now to understand when we are at the beginning of a new text. But to read the next text after the end of the current one, one has to use the 'next text' button which is not practical for corpora made of small texts.
Furthermore, if we consider a corpus as a sequence of texts - which is always the case (at least by construction/implementation, even if no chronological data is available) - texts reading navigation should modelize/help natural navigation from the last page of a text to the first of the next one.
h3. Solution A
Change the behavior of the 'next page' button: when the end of text is reached, display the first page of the next text if available.
Add a symetric behavior for 'previous page': when the beginning of text is reached, display the last page of the previous text if available.
h3. Diagnostic B
Current text edition navigation design uses 3 types of commands:
* next page, >
* end of text, >|
* next text, >>
It would be more intuitive for navigation (easier to learn) to balance behaviors between text pages navigation and texts navigation by adding navigation commands to 'last text' (aka end of corpus).
h3. Solution B
Add two additional commands and buttons to the Edition editor navigation toolbar:
* First text (go to first page of first text), |<<
* Last text (go to first page of last text), >>|
MD: both solutions implemented
MD: implemented also in the SynopticEditor
SH: we also need to implement this in the Portal edition