Document Home
Maintaining Teams and Players
Now that I have reached the point at which the application can record and edit what happens in a game, and can manage a schedule of games, I need to create some way to deal with the teams who are going to play in those games, and to assign players to those teams, right? I mean, gosh, a game is not a game unless someone is playing in it.
As I was musing about how to go about managing the records of teams and players, I realized that it would be nice to have some manner in which to routinely generate a table similar to that which I used in the previous section to edit the schedule for a given date. Much of the "heavy lifting" in an application like this is associated with the maintenance of relatively limited sets of data. As a result, the development of such a capability should substantially ease the effort associated with implementation of additional components. In this section, I will first leverage the experience garnered in the previous section to generate a generic subroutine that will display groups of records on a page that allows simultaneous addition, editing, and deletion. Once I have a working model of the subroutine I will apply it to the maintenance of schedule records, replacing the previous implementation. Once the working subroutine is in place I will use it to manage the records of teams and players.
1: Developing A Generic Editing Table Subroutine
2: Managing Team Records
3: Managing Player Records
4: Associating Players with Teams