Suggestion: Inline Display Toggle and Reducing Screen Clutter

Resources with inline displays (e.g., LDGNT, SGNT, interlinears, etc) are terribly crowded particularly on smaller devices. And so, it would be wonderful if some or all excess data could be eliminated. For example, the Lexham Discourse Greek New Testament (LDGNT) automatically displays Greek lemmas, morphology, Louw-Nida articles, and english glosses. All of this information overloads my screen. In contrast, The Lexham High Definition New Testament: ESV Edition (the English counterpart to LDGNT) looks good even on my Android phone. Why is that? It only displays only the most essential information (i.e., the manuscript). As a result, I can clearly view Steven Runge's analysis and comfortably read the text. I think that both tablet users and phone users would benefit from the option to toggle or eliminate excess data from resources that have inline displays. I hope the development team will consider solutions for this issue.

As a side note, more gradations in font choices would also help with screen clutter since present gradations are quite dramatic. I mean large is LARGE and small is ... you get the point. Wink

Thank you for all your hard work! I use the Android app almost every day.

Find more posts tagged with

Mobile App

Comments

Adam Olean

I thought it might be helpful if I make my example a little clearer by adding a few details.

While holding my phone horizontally, The Lexham High Definition New Testament: ESV Edition (HDNT) is able to display from 11 to 15 lines of bible text, depending on the font size whether it is normal or small. However, The Lexham Discourse Greek New Testament is able to display only 2 to 3 lines of bible text and very few words per line, often as little as 2 or 3 words while using the normal font size. Interestingly, the English characters of HDNT appear larger than the Greek characters of DGNT. The difference between these parallel resources, due to the inline display settings, is dramatic. This applies to any resource with an inline display.

Dave Hooton

https://community.logos.com/discussion/comment/339018#Comment_339018

I like to keep the inline display to a minimum with Interlinears in L4, and wouldn't mind a choice on Android. The good thing is that additional information is displayed when you long press a word (I don't know about HDNT/DGNT). In the case of Reverse Interlinears that's the only way to get original language information; which is great because I mainly want to read the ESV.

Adam Olean

https://community.logos.com/discussion/comment/339101#Comment_339101

Good points. I should have made a distinction between standard interlinears and resources like DGNT, since the whole point of interlinears is to display at least some information. Personally, I do not use interlinears; so, I would prefer to remove the excess information from DGNT. It and related resources are not very useful right now, especially with limited screen space.

The good thing is that additional information is displayed when you long press a word (I don't know about HDNT/DGNT).

I just tested this. Long pressing displays complete information for DGNT but not for HDNT. Long pressing HDNT only retrieves the visible English text.

Benjamin Tsao

https://community.logos.com/discussion/comment/339110#Comment_339110

Ditto... the logos android app is generally quite cluttered... perhaps the android development team could consider adding customization options to the interface. (e.g Margin size, fonts size, line spacing, fonts, turning off page turn animation, perhaps even touch to turn option - left for back, right for forward), Something like the Aldiko ebook reader App...i think they did a brilliant job with options for the interface.

Adam Olean

If anyone thinks interlinears are too cluttered on mobile devices and would like the option to toggle or reduce that information, consider voting for the following user-voice suggestion: https://logosmobile.uservoice.com/forums/190765-logos-mobile-apps/suggestions/3639767-display-discourse-ot-nt-resources-without-all-of-t

If you would like a solution that applies to all interlinears (not just discourse Greek/Hebrew interlinears), then remember to voice your opinion in the user-voice comments.