jdcr256 wrote:I see what you're getting at. This is a good idea. Unfortunately, applying it to this application opens up a lot of implications that are not readily apparent. I'll put it on the back log, but it may not be considered for implementation, at least in the short term.
What about the simple ability to create a class based on another class (a clone or copy operation)? In this case, the user could setup one of the classes, copy it to the other two and then edit the parts that are different (teachers, 1st Sundays, etc). Assuming there wasn't a permanent link between the classes, it seems like that wouldn't be so complicated. The user interface shouldn't be at least. But maybe there are backend issues that make a clone operation tricky.