Quote:
Originally Posted by cdcox
The HTML5 canvas part isn't that big of a deal. But now you have 22 bodies that you need to track in a very specific way during a play. Instead of maybe 10 that you only had to track in a general way. The simulation that you need to do to support an animation is probably 5 to 10 times more detailed than the one you need to run to support a text based simulation. So 5000 lines of code for a text based simulation becomes 30,000, plus the animation code. It can be done, but it isn't at all trivial.
|
Ah I think you are taking it far too far... I am talking something simple to start. Imagine that the ONLY data you had was what was already in the play by play that we read. Just take THAT data (and you would need the positional data if you wanted to be even more specific, for example on a QB sack it'd be cool to show which side it came from... but certainly not a dealbreaker) and with the simple play by play info you could create very crude animations of each play. RainMan may be right, I may have to draw this out to explain how simple I mean it to be. I am not even talking about showing all the players on the field or anything close to that. Just a simple animation of what we already read.