Before my efforts, I would place my hand on the results and slowly slide my hand down so each race would be revealed to me individually. This was not terrible but there was no race suspense as only each final result was revealed.
So I developed a Java application that would take a raceID, parse the HTML data from the race, and use the data to produce the race calls, call by call, so one would not see the final outcome until one clicked through each call.
Since I already had the parsed race data, I computed the internal race track calculations (e.g., Sartin Methodology). From these numbers, it was pretty easy to develop a crude image that would graphically represent these numbers -- each horse would be simply represented by a colored filled "line" going across the screen as the race unfolded. So before each race night, I would write down the set of my raceIDs (my big races would be at the bottom list so these would be my "featured races"). This made race night a fun event for me. Given it took me less than 20 hours to develop, I was extremely happy with my application.
When I told some Simsters about my fun race night, they wanted to try my race viewer. So I posted the Java byte code -- if one had a Java VM on their computer (which was quite common back then), they could run my race viewer.
As I said earlier, it was a very crude race viewer. It worked only with races that had internal calls so it would not work with QH races. You needed to first note and then enter in each raceID . The graphics/animation could have been much much better. But since I was pretty happy with my application and was pretty busy way back then (now I am retired so I tend to write rambling messages so I can relive the past), I never did a major upgrade of the application.