jerryshi042003
commented
1 month ago A good first start to this is creating "Simple Tagger"
So instead of every shot's info, this is bare minimum to still be useful and have some summary stats. The metrics needed to be recorded are
Time Start, Time End of each point First Serve Result (Ace, In, Out) If First Serve Out: Second Serve Result (Ace, In, Out) Who hit last shot: What happened last shot: Winner, Forced Error, Unforced Error --> Determines who won the point
Fredenck
Overview
CJ, Pavan are developing a new set of buttons similar to those in taggerButtonData. This could be for doubles, etc.
Add a field to the upload match button that allows the person to choose what tagger to use for the match being uploaded.
Development
Ideally, the tagger button data would be stored in firebase and queried dynamically but I haven't thought of a practical way to do this. If you can't think of one either it's okay to hardcode the options into the upload form as well as hardcoding multiple versions of the tagger. Off the top of my head, create an object that maps strings to tagging panels
{'doubles': doublesTaggingButtons}for example, and then query the keys of this when making the object.Don't just pile more button data pages into services. Maybe make a separate directory for taggers or put them all in an array in the taggerButtonData file (the former makes more sense to me). Make this expandable, so that we can easily add a new tagger in the future (by adding an entry to the object as well as exporing a new tagger for example).