Use Last O/D Line
o2bnited opened this issue · comments
One user told me that it would be useful to be able to clear all the players at once, and also to save certain groups of players since many teams are running lines of O and D that could be reused to speed up that process.
I have no sense of how difficult this would be to implement but I can see it being rather useful if it is easy to do--this might minimize button presses for the substitution process.
(Subject edited by cboulay. Original subject was "substitutions: clearing and defaults")
Issue #46 is about removing all players at once.
As for saving groups of players, that might finally be workable for AUDL. It was requested of me in Ultistats for iPhone only once by somebody from Florida who used the words "cool" and "bro" about 10 times in a one-paragraph e-mail. My answer then was that rosters fluctuated too much from tournament to tournament and game to game (injuries, people leaving to catch a plane), and editing these prepared lines was as much work as entering the O line (or D-line) once at the beginning of a game and having the option to "Use last O-line" or "Use last D-line" on subsequent points.
Quick aside: Adding "Use last O-line" and "Use last D-line" buttons is something that I'd like to do but there are a few things higher up the priority list.
With the AUDL I expect rosters to be more consistent across games and thus the lines to be more consistent. Additionally, if the stat keeper knows the team they probably know well in advance if the lineups are going to be changed so this could potentially let them do some of the work in advance.
Thinking from an AUDL perspective only, if you had to prioritize, in what order would you rank the following?
- Clear All (#46)
- Use last O|D line
- Set the line using one of many pre-saved templates.
On a programming difficulty scale from 1-10, 10 being the hardest, the first is about a 2, the second is about a 4, and the third is about a 12 (it'd be about an 8 in a native app).
I would say that clear all and starting with the last O line or D line should be sufficient, and I think I would say that assuming that "use last O line" would take all players on the virtual field and replace them with the last o line used for that team, then I would prioritize the "use last O/D line" ahead of "clear all".
I'm not sure how other teams are doing it, and I don't want to reveal too much about how we are doing lines, but I don't think that the app needs to be able to use one of many pre-saved templates given the amount of work required to implement that feature.
OK. I'll get started on the Use Last button as soon as I finish up with my current project. I won't assign this to myself just yet because my current project is a big one and it might take some time.