BUG with SUGG: Reading plans
I have been using reading plans very often for non-Bible books. I use the plans as group plans and then read through books with people in my church. This has become an awesome tool for discipleship!!!
The issue is that (especially in vyrso books), the reading plans need to be hacked to work. What I mean is that the plan acts as if the cover, title page, and table of contents take forever to get through. In order to make a 10 week plan on a book plan that I started today, I had to trick Logos by making it a 14 week plan starting last month. Then we Catch-up to today and get started. It seems like this bug should be fixable. Here's a video of what scrolling through that plan looks like: http://screencast.com/t/fPDuVgap. It's like it thinks of each section as equivalent regardless of length. This should not be so.
My suggestions:
- Allow us to specify a page range (or chapter range) with the plan. This would be much like the current print dialog
: - Have the app be more careful about assigning reading length in non-versified resources based on content length (character or word count).
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org
Comments
-
hi Jacob
Fully agree, great suggestions.
Graham
0 -
suggestion 3: In books without pagination (Maybe only vyrso books, but Gospel Deeps is a good example of the problem), a reading plan with daily reading won't put markers throughout the chapter. Rather every few days the reading plan calls for reading an entire chapter with nothing on the days in between. The reading plan should function the same on paginated and non-paginated resources and should base its work off of word count.
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
Jacob Hantla said:
suggestion 3: In books without pagination (Maybe only vyrso books, but Gospel Deeps is a good example of the problem), a reading plan with daily reading won't put markers throughout the chapter. Rather every few days the reading plan calls for reading an entire chapter with nothing on the days in between. The reading plan should function the same on paginated and non-paginated resources and should base its work off of word count.
Another great suggestion[Y]
0 -
I am hoping for fine control over reading plans, irrespective of page number, chapter heading, etc. Those can be useful, but not always.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
alabama24 said:
I am hoping for fine control over reading plans, irrespective of page number, chapter heading, etc. Those can be useful, but not always.
I would love as much control as possible. However, for the sake of simplicity and because an interface design already exists (in the print dialog) for finer control, I was recommending it as something that might be easy enough to more quickly more to market. The reading plan generator is definitely a problem for the desktop app, especially considering the prominent focus that reading plans have taken in the mobile apps, faithlife, and web.
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
We have several active cases relating to improving the Reading Plan tool. I couldn't give you any information about scheduling, but it is something on our radar. Thank you for the suggestions, I'll find the most appropriate case to update with a link to this thread.
0
