SplitsBrowser doesn't presently handle age classes all that well. What it refers to internally as an 'age class' isn't always an age class. A better name should be used instead.
Additionally, SplitsBrowser should also make some attempt to read in a competitor's age class and store it with a competitor. This would allow SplitsBrowser's input-data parsing to be used elsewhere: one suggested idea is for a league-table calculator.
SplitsBrowser doesn't presently handle age classes all that well. What it refers to internally as an 'age class' isn't always an age class. A better name should be used instead.
Additionally, SplitsBrowser should also make some attempt to read in a competitor's age class and store it with a competitor. This would allow SplitsBrowser's input-data parsing to be used elsewhere: one suggested idea is for a league-table calculator.