OOP344 - Team Nothing - 20102

OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

Participants

Team Members

OOP344 - Team Nothing - 20102

ID	First Name	Last Name	Section	Seneca Id	wiki id	IRC nick	Blog URL
A	Alex	Chung	A	acchung1	acchung1	acchung1	my blog
B	Don Armin	Napao	A	danapao	danapao	danapao	My Blog
C	Robin	Co	A	rco1	imadorki3	rco1	My Blog
D	Bhavanesh	Patel	A	bapatel5	bapatel5	Bhavanesh	My Blog

Team Contact Person

Alex Chung - acchung1

Project Development Page

Project Development Page

IRC Chatlogs / Meeting Logs

IRC meeting logs

30-May-2010

Channel #Team-Nothing

10-June-2010

Channel #Team-Nothing

We decided as a group to talk in class, or through e-mail as our means of communications because everyone is available at different times.

Responsibilities

The responsibilities are based off of the different Classes. 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

IOField

Name: Alex Chung

IOLabel

Name: Bhavanesh Patel

IOEdit

Name:

IOForm

Name:

IOVEdit

Name:

IOTextEdit

Name:

Conventions and Styles

Function Conventions

Function Naming Convention

Function names are all lowercase and each word is separated by an underscore character.

int do_something()
{
  code;
}

Function Comments

Each function definition should include a comment above it that includes the function name, a brief and clear description of what each variable does in the function, and a clear and concise description of what the function does.

/*
 * Function Name: function_name
 * Description: This is a clear and concise function description.
 * Variable: variable1 - this variable holds the value of something for some purpose
 *           variable2 - this variable holds the value of something else for some other purpose
 */
int function_name()
{

  code;

}

Variable Conventions

Naming Convention

Similar to the 4.1 Function Naming Convention

For Compound Variable Names:

int some_var;

OR

For Non-compound Variable Names:

int var;

Variable Definitions

Define each variable on a speparate line.

int var1;
int var2;

File Headings

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 (Team Nothing) and description of what the file does. The description should be clear and concise. This must be enclosed using /* and */.

/*
 * File Name: example.cpp
 * Author: Team Nothing
 * Description: This is a clear and concise description of the file.
 */

Indentation Level

Use an indentation level of two spaces in all situations. Do not use TAB for indentation.

int some_function()
{

   code;
   more code;

}

Curly Braces

Each { and } for a code block, such as in an if statement or a for loop, should be placed on 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 one line of code, continue to use the curly braces for clarity and in case additional code is added afterwards.

void function()
{
   if(some-condition)
   {
      code;
   }
}

if(some-condition)
{
   code;
}
else
{
   code;
}

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_HEADERFILE_H_
#define _TN_HEADERFILE_H_