There are, of course, lots of different possible approaches to achieving timetabled operation: some of them more flexible (and requiring more coding work to set them up) and some of them more limited (requiring less coding work to set them up). I believe that I have defined earlier in the thread what I consider to be an ideal system within the bounds of what can realistically be achieved if those who are inclined to do this sort of work are inclined to spend sufficient time doing so. Whether they are, of course, is another matter entirely, and no criticism is intended if they are not: this is, as Bob pointed out, a hobby for all concerned.
There is much to be said, however, for the view that, if one is proposing to spend a considerable effort coding a new feature, it is optimum to assess the requirements for that feature carefully before one starts and plan how those requirements can best be implemented, as doing so can make the overall amount of time spent fulfilling those requirements in the long term rather less than if one implements a system that fulfils some but not all requirements, but which cannot easily be expanded to fulfil other, closely related requirements.
James E. Petts