Changes

[http://zenit.senecac.on.ca/wiki/index.php/{{OOP344 | OOP344] | [http://zenit.senecac.on.ca/wiki/index.php/OOP344_Weekly_Schedule_20102 Weekly Schedule] | [http://zenit.senecac.on.ca/wiki/index.php/Student_List_OOP344 Student List] | [http://zenit.senecac.on.ca/wiki/index.php/Teams_OOP344 Teams] | [http://zenit.senecac.on.ca/wiki/index.php/Project_20102_OOP344 Project] | [http://zenit.senecac.on.ca/wiki/index.php/IRC_Schedules_OOP344 IRC Schedules] | [http://zenit.senecac.on.ca/wiki/index.php/Student_Resources_OOP344 Student Resources]Index}}

 =1.0 Participants===1.1 Team Members==

=Responsibilities= 1The responsibilities are based off of the different Classes.2 Team Contact Person Each person is responsible for at least one of the class.If it is incomplete, they need to state it in the Bugs / Completed Tasks or somewhere that everyone can see.==The Application=====IOFrame===Name: Alex Chung====IOFrame Bugs / Completed Tasks====* completed the functions but have yet to test for bugs* unsure if the functions are created properly but it is compilable :)* need to make test program for this===IOField===Name: Alex Chung====IOField Bugs / Completed Tasks====* completed the functions but have yet to test for bugs* unsure if the functions are created properly but it is compilable :)* need to make test program for this*unsure of what it means by "enforces the children to do ..." '''*Solved*'''

'''[mailto===IOLabel===Name:kmsingh@learn.senecac.on.ca Kerry Singh]''' <brBhavanesh Patel====IOLabel Bugs />'''IRC Nick: sinker'''Completed Tasks====

=2.0 Project Development Page==IOForm===[[OOP244 - Team Nothing Project Dev Page - 20101 | Project Development Page]]Name: Robin====IOForm Bugs / Completed Tasks====

=3.0 IRC Chatlogs ==Linked List / Meeting LogsDynamic Array===Alex: I created a linked list but unsure if you want to use dynamic arrayEach node stores 1 character[[OOP344 - Team Nothing IRC Logs - 20102 | IRC meeting logs]]=Conventions and Styles===Function Conventions=====Function Naming Convention=3.1 30-May-10==[[OOP344_-_Team_Nothing_IRC_Logs_-_20102#30-May-10 Channel: #Team-Nothing|Channel #Team-Nothing]]Function names are all lowercase and each word is separated by an underscore character.

==4.2 Variable ConventionConventions=====4.2.1 Naming Convention===

For CompoundVariable Names:

For SingleNon-compound Variable Names:

===4.2.2 CreatingVariable Definitions===Each Define each variable should be on it's own a speparate line.

==4.3 Indent Level==The indent level in any case will consist of three spaces. There will be no tab use. <pre>int someFunction{  code; more code; }</pre> ==4.4 File HeadingHeadings==Each file with the extension of *.cpp, *.c, and *.h must include a comment heading at the beginning of the file stating the file name, author (and usernameTeam Nothing), date created, last modified date, and description of what the file does. The description should be clear and concise. This must be enclosed using /* and */.

* Author: Name (senecaid) * Create Date: 23-May-10 * Last Modified Date: 11-Nov-10Team Nothing * Description: blah blah blahThis is a clear and concise description of the file.

==4.5 Function CommentsIndentation Level==Each function should include a comment above the function similar to the file heading ([[OOP344_-_Team_Nothing_-_20102#4Use an indentation level of two spaces in all situations.4 File Heading|4Do not use TAB for indentation.4 File Heading]]), except only including the function name, what each variable does in the function, and a description of what the function does 

/* * Function Name: function_name * Description: Blah blah blah. * Variable: variable1 - this does this to this function * variable2 - this is 2 */int function_namesome_function()

code; more code;

==4.6 Curly Braces==Use of Each { and } in for a code block, such as in an if statement, or a for loop, should start be placed on a new its own separate line, with the { and } lined up with the first character of the line above it. If the code block consists of only has one coded line for the resultof code, please continue to use the curly brackets anyways braces for readability’s sakeclarity and in case additional code is added afterwards.

==4.7 Conditional Compilation=====Naming Convention for Header Files===Prefix the names of header files that we create with "tn" (initials of Team Nothing) followed by an underscore character. For example, tn_headerfile.h When using conditional compilation, use the following format for a file named tn_headerfile.h:

#ifndef _tn_headerfilename_h_TN_HEADERFILE_H_#define _TN_HEADERFILE_H_