My favorites | Sign in
Project Logo
                
Search
for
Updated Nov 14, 2008 by brandoughty
Labels: Featured, Phase-Design
ToResolve  
Unresolved design issues

"Who should decide" is the "Decider(s)" (think Bush); but everyone is welcome to advise them (Think Cheney).

I tried to make the deciders the people whose routines' complexity is most affected. Correct me if I'm wrong. Also correct if you need to know/not. Main (Michael) needs to know most, but usually just to allot sizes/names.

Issue Who should decide Who needs to know
PipeH[ ] Byte size or Word? So far only stores Y/N. Will be a Word All (Almost)All
PipeH[ j] value Y/N: 0 for yes, NOT(0) for no? Will be 0x00 for no and 0xFF for yes Thomas?? (Almost)All
Squares[ ] will keep track of sides. Using Thomas' proposed structure in ProcedureInitial or some variation thereof. Brandon, Dayton, Bailey Brandon, Dayton, Bailey, Thomas, Stacey
Squares[ ] IsSquare? and WhoseSquare? are both potentially bit-size. Format for storing (thus format for Squares[ ] Thomas proposed a structure in ProcedureInitial. Brandon, Dayton, Stacey Brandon, Dayton, Thomas, Stacey
LastPipe (pipe just played) format: The offset of LastPipe will be passed and stored in a word so that the most significant bit of the word can be set to signify if the pipe is either Horizontal or Vertical. 0=Horizontal 1=Vertical Brandon, Jamie-Leigh, Dayton Stacey, Bailey, Brandon, Dayton, Jamie-Leigh
Player (2 players, or computer), how stored in computer, how represented in Squares, output board, connection Michael, (Stacey, Brandon OR Dayton) Michael, Stacey, Brandon, Dayton
Boundaries between Brandon's and Dayton's: Brandon calculates if there's a square and changes Squares[ ] for that. Dayton marks WhoseSquare? Brandon, DaytonBrandon, Dayton
Common code/procedure? Jamie & Bailey are going to do the code independently and then have the option of asking each other for assistance if needed Jamie, Bailey Jamie, Bailey



Sign in to add a comment
Hosted by Google Code