Extending length of or adding new parts to the Dr. Horner reading plan

[ispringle]

Is your feature request related to a problem? Please describe.

The Dr. Horner Reading plan can go on almost indefinitely. I ran the LCM on it and it'd take 16,014,419,000 years to get back to the start of the plan. The plan provided in this app only covers the first 366 days of the plan.

Describe the solution you'd like

Either add additional days to the plan or create follow-up plans for year 2, 3, etc.

Describe alternatives you've considered

I currently am building my own reading plan files to extend past year one.

Additional context

I've written tooling to create an infinitely long reading plan for Dr Horner's Reading Plan. I'd be happy to put in the effort to implement this, just need to know which way to go with it (extend or additional years).

[timbze]

Hey thanks for opening an issue. We would very much welcome work on the reading plan feature in AndBible. I have done some work on them but unfortunately have had little time to work on the project in the last few years.

Having said that, I am not sure that just building a feature to make an infinite reading plan would be the most helpful, though maybe it would be and you'd convince me once you say how you would do it.

I had planned some UX improvements in #2095 but did not get too far and currently cannot see when I will be able to continue.

I think your idea could go well with what I was thinking in #2095, where I tried to make it more date-friendly. There would be a horizontal bar showing date or plan day # instead of how it is now. You can start something entirely different if you like, but if you could give your ideas on what you would like to implement that would be great to hear! The reading plans could use a lot of improvements.

[ispringle]

I hadn't thought of anything grand, but I do agree that the reading plan portion of the app could use some love. I've been using AndBible for the Dr. Horner reading plan more or less continuously since 2018, I've found work arounds for much of the pain points by this point.

My original idea when I made this issue was to provide either a multi-year plan file or files for subsequent years. Currently I'm generating a new file every year or so and manually adding it to the app. It looks like I haven't committed any reading plans to GitHub other than a plan for the first four years. A generator would definitely make the most sense for this particular plan, but since most plans have a finite length, it seems like that might be a lot of effort for such a small use case.

I'll take a look at #2095 and also refresh myself on the painpoints I've found and get back to you. Thanks so much for the reply!