By Monday, March 1, all of the CampEditor screens will be coded in VC. The Default Setting screens as well as the New Camp wizard will be completed after Spring Break. We have created a checklist of all of the user interface screens, whether or not they have been coded yet, and any notes regarding their status.
Carla and Sara started researching how to save the camp files to be used/opened later. Object Serialization seems to fit our needs of persistent objects; we will continue this research next week. We also found some other classes that will be very useful in coding the major classes for our project (i.e. CTime, CTimeSpan, CObList, CPtrList, CStringList).
A TimeSlot is going to be a linked-list of Nodes. These Nodes contain in them a Court, a starting time, the session#, the two teams playing in that Court at that time, and the league those teams are in. Each TimeSlot is also part of a list pointed to by Camp, and it contains its time, session# and the list of Nodes. The apparent redundancy in having time and session# in both the Nodes and the TimeSlot is necessary for our bigger algrithm.
We have also decided on a little different strategy for the main scheduling
algorithm. There will be a member function of Camp called "scheduleCamp()",
but there will be several levels of algorithms that this function calls.
So, rather than one mega-algorithm, we are going to have a few large alorithms.
This will make coding and testing much easier. We will have the .cpp files
for our Node and TimeSlot classes done by Spring Break, along with as many
other classes as we can get done next week. Then, we'll start work
on the big functions when we get back.
Email the producer (Sara Bidgood)