1
edit
Changes
→IOTextEdit Bugs / Completed Tasks
{{OOP344 Index}} =1.0 Participants===1.1 Group Team Members==
{| class="wikitable sortable" border="1" cellpadding="5" align="center"
|+ OOP344 - Team Nothing - 20102
|-
| A ||[[User:acchung1 | Alex]] || Chung|| A || [mailto:acchung1@learn.senecac.on.ca acchung1] || [[Special:Contributions/acchung1 | acchung1]] || acchung1 || [http://acchung1.blogspot.com/ my blog]
|-
| C||[[User:imadorki3 | Robin]] || Co || A||[mailto:rco1@learn.senecac.on.ca rco1] || [[Special:Contributions/imadorki3 | imadorki3]] || rco1 || [http://imadorki3.blogspot.com/ My Blog]
|-
| D||[[User:bapatel5 | Bhavanesh]] || Patel || A||[mailto:bapatel5@learn.senecac.on.ca bapatel5] || [[Special:Contributions/bapatel5 | bapatel5]] || Bhavanesh || [http://bhavanesh.wordpress.com/ My Blog]
|-
|}
=2=Team Contact Person==Alex Chung - [mailto:acchung1@learn.senecac.on.0 ca acchung1]=Project Development Page=[[OOP244 OOP344 - Team Nothing Project Dev Development Page - 20101 20102 | Project Development Page]]
=3.0 IRC Chatlogs / Meeting Logs=
[[OOP344 - Team Nothing IRC Logs - 20102 | IRC meeting logs]]
==30-May-2010==
[[OOP344_-_Team_Nothing_IRC_Logs_-_20102#30-May-10 Channel: #Team-Nothing|Channel #Team-Nothing]]
==10-June-2010==
[[OOP344_-_Team_Nothing_IRC_Logs_-_20102#10-June-10 Channel: #Team-Nothing|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
====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*'''
===IOLabel===
Name: Bhavanesh Patel
====IOLabel Bugs / Completed Tasks====
===IOEdit===
Name: Bhavanesh Patel
====IOEdit Bugs / Completed Tasks====
===IOForm===
Name: Robin
====IOForm Bugs / Completed Tasks====
===IOVEdit===
Name:
====IOVEdit Bugs / Completed Tasks====
===IOTextEdit===
Name:
====IOTextEdit Bugs / Completed Tasks====
* BCKSPACE key bug fixed***
* PG_DWN key is currently buggy and not working properly
===Linked List / Dynamic Array===
Alex: I created a linked list but unsure if you want to use dynamic array
Each node stores 1 character
=Conventions and Styles=
==Function Conventions==
===Function Naming Convention===
Function names are all lowercase and each word is separated by an underscore character.
<pre>
int do_something()
{
code;
}
</pre>
===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.
<pre>
/*
* 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;
}
</pre>
==Variable Conventions==
===Naming Convention===
Similar to the [[OOP344_-_Team_Nothing_-_20102#4.1 Function Naming Convention|4.1 Function Naming Convention]]
For Compound Variable Names:
<pre>
int some_var;
</pre>
OR
For Non-compound Variable Names:
<pre>
int var;
</pre>
===Variable Definitions===
Define each variable on a speparate line.
<pre>
int var1;
int var2;
</pre>
==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 */.
<pre>
/*
* File Name: example.cpp
* Author: Team Nothing
* Description: This is a clear and concise description of the file.
*/
</pre>
==Indentation Level==
Use an indentation level of two spaces in all situations. Do not use TAB for indentation.
<pre>
int some_function()
{
code;
more code;
}
</pre>
==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.
<pre>
void function()
{
if(some-condition)
{
code;
}
}
if(some-condition)
{
code;
}
else
{
code;
}
</pre>
==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:
