Difference between revisions of "OOP344 ASOS"

From CDOT Wiki
Jump to: navigation, search
(→‎Wen Fang Chen)
Line 1: Line 1:
−
 
+
[[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093 |OOP344 IRC Schedules]]<br />
−
== [[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093 |OOP344 IRC Schedules]]<br />
 
  
 
= ASOS Brigade - Team 6 =
 
= ASOS Brigade - Team 6 =
−
SVN: ops344_093a06
 
−
{| border="1" cellpadding="5"
 
−
 
−
|+ [[ ASOS Brigade| ASOS Brigade]]
 
−
! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! Current Task !! SVN ID
 
−
|-
 
−
| Zhang || Shun Yao || syzhang4 || C || [http://shunyao-CPA.blogspot.com/ MY Blog] || DownWind || IO_MenuBar ||64
 
−
|-
 
−
| Hong || Yong || yhong17 || B || [http://xderick.blogspot.com/ xDerick' Blog] || Yong_Clicker || IO_Form, IO_Frame, IO_Field || 65
 
−
|-
 
−
| Kim || Taehoon || tkim28 || B || [http://hoonkoon.blogspot.com/ Blog] || hoongoon || IO_Radio || 66
 
−
|-
 
−
| Chen || Wen Fang || wfchen || C || [http://wenfangchen.blogspot.com/ Gwen's Blog] || Gwen2009 || IO_Label || 62
 
−
|-
 
−
| Xue || Yong  || yxue11 || C || [http://opp344-yxue.blogspot.com/ Blog] || yxue11 || IO_Edit,IO_Vedit|| 67
 
−
|-
 
−
| Tran || Chi-Lea || ctran13 || C || [http://ctran13.blogspot.com Nitty Gritty] || ctran13 || ciol.c, IO_TextEdit|| 61
 
−
|-
 
−
| Tran || Victor || vvtran || C || [http://victran.blogspot.com Blog?] || victran || IO_CheckList  || 63
 
−
|-
 
−
| Wang || Cong || cwang84 || B || [http://wangcong422.blogspot.com Blog] || cwang84 || IO_Menu  || 68
 
−
|-
 
−
! Contact: !! - !! - !! - !! - !! - !! - !! -
 
−
|-
 
−
| Tran || Chi-Lea || - || - || - || - || -  || -
 
−
|-
 
−
| Chen || Wen Fang || - || - || -|| - || -|| -
 
−
|-
 
−
|}
 
  
 
= Project Overview =
 
= Project Overview =
Line 41: Line 11:
 
== 1.2 Class Overview ==
 
== 1.2 Class Overview ==
  
 +
    This is incomplete!
  
  
Line 55: Line 26:
 
Email: wfchen@learn.senecac.on.ca
 
Email: wfchen@learn.senecac.on.ca
  
−
2.2 Group Members
+
== 2.2 Group Members ==
  
−
Wen Fang Chen
+
=== Wen Fang Chen ===
  
 
IRC Username: Gwen2009
 
IRC Username: Gwen2009
Line 67: Line 38:
 
Email: wfchen@learn.senecac.on.ca
 
Email: wfchen@learn.senecac.on.ca
  
−
Yong Hong
+
=== Yong Hong ===
  
 
IRC Username: Yong_Clicker
 
IRC Username: Yong_Clicker
Line 77: Line 48:
 
Email: rod1205@hotmail.com
 
Email: rod1205@hotmail.com
  
−
Taehoon Kim
+
=== Taehoon Kim ===
  
 
IRC Username: hoongoon
 
IRC Username: hoongoon
Line 85: Line 56:
 
Blog: http://hoonkoon.blogspot.com/
 
Blog: http://hoonkoon.blogspot.com/
  
−
Email:                                                   hoongoon86@hotmail.com
+
Email: hoongoon86@hotmail.com
  
−
Chi-Lea Tran
+
=== Chi-Lea Tran ===
  
 
IRC Username: ctran13
 
IRC Username: ctran13
Line 97: Line 68:
 
Email: ctran13@learn.senecac.on.ca
 
Email: ctran13@learn.senecac.on.ca
  
−
Victor Tran
+
=== Victor Tran ===
  
 
IRC Username: victran
 
IRC Username: victran
Line 107: Line 78:
 
Email: victor.vy.tran@gmail.com
 
Email: victor.vy.tran@gmail.com
  
−
+
=== Cong Wang ===
−
 
 
−
Cong Wang
 
  
 
IRC Username: cwang84
 
IRC Username: cwang84
Line 119: Line 88:
 
Email: cwang84@learn.senecac.on.ca
 
Email: cwang84@learn.senecac.on.ca
  
−
Shun Yao Zhang
+
=== Yong Xue ===
 +
 
 +
IRC Username: yxue11
 +
 
 +
Section: C
 +
 
 +
Blog: http://opp344-yxue.blogspot.com/
 +
 
 +
Email: yxue11@learn.senecac.on.ca
 +
 
 +
=== Shun Yao Zhang ===
  
 
IRC Username: DownWind
 
IRC Username: DownWind
Line 129: Line 108:
 
Email: syzhang4@learn.senecac.on.ca
 
Email: syzhang4@learn.senecac.on.ca
  
−
Yong Xue
+
= 3.0 SVN Repository =
  
−
IRC Username: yxue11
+
== 3.1 Address == 
 +
    svn://zenit.senecac.on.ca/ops344_093a06 
 +
 
 +
== 3.2 Usernames and Logins ==
 +
 
 +
    Normal  0              false  false  false      EN-US  X-NONE  X-NONE                                                    MicrosoftInternetExplorer4
 +
 
 +
Wen Fang Chen: ops344_093svn62
  
−
Section: C
+
Yong Hong: ops344_093svn65
  
−
Blog: http://opp344-yxue.blogspot.com/
+
Taehoon Kim: ops344_093svn66
  
−
Email: yxue11@learn.senecac.on.ca
+
Chi-Lea Tran: ops344_093svn61
  
−
+
Victor Tran: ops344_093svn63
−
+
Cong Wang: ops344_093svn68
  
−
3.0 SVN Repository
+
Yong Xue: ops344_093svn67
  
−
3.1 Address  svn://zenit.senecac.on.ca/ops344_093a06  3.2 Usernames and Logins   
+
Shun Yao Zhang: ops344_093svn64
−
 
  
−
4.0 Conventions and Styles
 
  
−
4.1 File headings
+
= 4.0 Conventions and Styles =
  
−
+
== 4.1 File headings ==
  
−
                Each file with the extension of *.cpp, *.c, and *.h must include a comment heading stating the file name, author (and username), 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 */.  For example:
+
Each file with the extension of *.cpp, *.c, and *.h must include a comment heading stating the file name, author (and username), 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 */.  For example:
  
−
 
  
 +
<pre>
 
/*
 
/*
  
Line 168: Line 152:
  
 
*/
 
*/
 +
</pre>
 +
== 4.2 Function Comments ==
  
−
4.2 Function Comments
+
Each function should include a comment above the function similar to the file heading (4.1), except only including the function name and a description of what the function does.  For example:
−
 
 
−
 
−
 
 
−
                Each function should include a comment above the function similar to the file heading (4.1), except only including the function name and a description of what the function does.  For example:
 
−
 
 
−
 
  
 +
<pre>
 
/*
 
/*
  
Line 192: Line 173:
  
 
}
 
}
 +
</pre>
  
−
4.3 Inline Comments
+
== 4.3 Inline Comments ==
−
 
 
−
 
−
 
 
−
                Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code in that general area.  Please use inline comments wherever the code might be confusing for others to understand.
 
−
 
 
−
4.4 Indent level
 
  
−
   
+
Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code in that general area. Please use inline comments wherever the code might be confusing for others to understand.
  
−
                All documents must have indentation when writing code in a code block. The indent level in any case will consist of two spaces.  There will be no tab use. For example:
+
== 4.4 Indent level ==
−
 
 
−
 
  
 +
All documents must have indentation when writing code in a code block.  The indent level in any case will consist of two spaces.  There will be no tab use. For example:
 +
<pre>
 
int someFunction
 
int someFunction
  
Line 217: Line 193:
 
}
 
}
  
−
+
</pre>
−
 
 
−
4.5 Curly Bracket Use
 
−
 
 
−
 
  
−
                Use of { } in a code block, such as in an if statement, a for loop, should start on a new line, with the { } lined up with the first character of the line above it.  If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake.  For example:
+
== 4.5 Curly Bracket Use ==
  
−
   
+
Use of { } in a code block, such as in an if statement, a for loop, should start on a new line, with the { } lined up with the first character of the line above it. If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake.  For example:
  
 +
<pre>
 
if ( mapleLeafs == lose)
 
if ( mapleLeafs == lose)
  
Line 234: Line 207:
  
 
}
 
}
 +
</pre>
  
−
4.6 Variable Naming Conventions
+
== 4.6 Variable Naming Conventions ==
−
 
 
−
 
−
 
 
−
                Variables should follow regular programming conventions ( must start with lowercase letter, no symbols…).  Variables should be descriptive for better understanding of it’s For example:
 
  
−
   
+
Variables should follow regular programming conventions ( must start with lowercase letter, no symbols…). Variables should be descriptive for better understanding of it’s For example:
  
 +
<pre>
 
int someVar;
 
int someVar;
 +
</pre>
  
−
4.7 Function Naming Conventions
+
== 4.7 Function Naming Conventions ==
−
 
 
−
             
 
  
 
Function names should start with a capital letter.  For example:
 
Function names should start with a capital letter.  For example:
  
−
+
<pre>
−
 
 
 
int SomeFunction()
 
int SomeFunction()
 +
{
 +
  code;
 +
}
 +
</pre>
  
−
{
 
  
−
  code;
+
{| border="1" cellpadding="5"
  
−
}
+
|+ [[ ASOS Brigade| ASOS Brigade]]
 +
! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! Current Task !! SVN ID
 +
|-
 +
| Zhang || Shun Yao || syzhang4 || C || [http://shunyao-CPA.blogspot.com/ MY Blog] || DownWind || IO_MenuBar ||64
 +
|-
 +
| Hong || Yong || yhong17 || B || [http://xderick.blogspot.com/ xDerick' Blog] || Yong_Clicker || IO_Form, IO_Frame, IO_Field || 65
 +
|-
 +
| Kim || Taehoon || tkim28 || B || [http://hoonkoon.blogspot.com/ Blog] || hoongoon || IO_Radio || 66
 +
|-
 +
| Chen || Wen Fang || wfchen || C || [http://wenfangchen.blogspot.com/ Gwen's Blog] || Gwen2009 || IO_Label || 62
 +
|-
 +
| Xue || Yong  || yxue11 || C || [http://opp344-yxue.blogspot.com/ Blog] || yxue11 || IO_Edit,IO_Vedit|| 67
 +
|-
 +
| Tran || Chi-Lea || ctran13 || C || [http://ctran13.blogspot.com Nitty Gritty] || ctran13 || ciol.c, IO_TextEdit|| 61
 +
|-
 +
| Tran || Victor || vvtran || C || [http://victran.blogspot.com Blog?] || victran || IO_CheckList  || 63
 +
|-
 +
| Wang || Cong || cwang84 || B || [http://wangcong422.blogspot.com Blog] || cwang84 || IO_Menu  || 68
 +
|-
 +
! Contact: !! - !! - !! - !! - !! - !! - !! -
 +
|-
 +
| Tran || Chi-Lea || - || - || - || - || -  || -
 +
|-
 +
| Chen || Wen Fang || - || - || -|| - || -|| -
 +
|-
 +
|}
 +
==

Revision as of 00:33, 11 November 2009

OOP344 - OOP344 Student List - OOP344 Teams - OOP344 Assignment One - OOP344 Assignment Two - OOP344 IRC Schedules

ASOS Brigade - Team 6

Project Overview

Project Description

The purpose of this project is to build a working command line text editor. It will be built from the ground up with an open source mentality using C/C++. We will be using an SVN repository in order to keep all of our files updated and organized, and to keep overwriting errors to a minimum. Our wiki page will also spell out our direction and any other information needed.

1.2 Class Overview

    This is incomplete!


2.0 Participants

2.1 Group Contacts

Chi-Lea Tran

Email: ctran13@learn.senecac.on.ca

Wen Fang Chen

Email: wfchen@learn.senecac.on.ca

2.2 Group Members

Wen Fang Chen

IRC Username: Gwen2009

Section: C

Blog: http://wenfangchen.blogspot.com/

Email: wfchen@learn.senecac.on.ca

Yong Hong

IRC Username: Yong_Clicker

Section: B

Blog: http://xderick.blogspot.com/

Email: rod1205@hotmail.com

Taehoon Kim

IRC Username: hoongoon

Section: B

Blog: http://hoonkoon.blogspot.com/

Email: hoongoon86@hotmail.com

Chi-Lea Tran

IRC Username: ctran13

Section: C

Blog: http://ctran13.blogspot.com/

Email: ctran13@learn.senecac.on.ca

Victor Tran

IRC Username: victran

Section: C

Blog: http://victran.blogspot.com/

Email: victor.vy.tran@gmail.com

Cong Wang

IRC Username: cwang84

Section: B

Blog: http://wangcong422.blogspot.com/

Email: cwang84@learn.senecac.on.ca

Yong Xue

IRC Username: yxue11

Section: C

Blog: http://opp344-yxue.blogspot.com/

Email: yxue11@learn.senecac.on.ca

Shun Yao Zhang

IRC Username: DownWind

Section: C

Blog: http://shunyao-cpa.blogspot.com/

Email: syzhang4@learn.senecac.on.ca

3.0 SVN Repository

3.1 Address

    svn://zenit.senecac.on.ca/ops344_093a06

3.2 Usernames and Logins

    Normal   0               false   false   false      EN-US   X-NONE   X-NONE                                                     MicrosoftInternetExplorer4

Wen Fang Chen: ops344_093svn62

Yong Hong: ops344_093svn65

Taehoon Kim: ops344_093svn66

Chi-Lea Tran: ops344_093svn61

Victor Tran: ops344_093svn63 Cong Wang: ops344_093svn68

Yong Xue: ops344_093svn67

Shun Yao Zhang: ops344_093svn64


4.0 Conventions and Styles

4.1 File headings

Each file with the extension of *.cpp, *.c, and *.h must include a comment heading stating the file name, author (and username), 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 */. For example: 


/*

File Name: example.cpp

Author: Victor Tran (victran)

Date: 27-Oct-09

Description: blah blah blah

*/

4.2 Function Comments

Each function should include a comment above the function similar to the file heading (4.1), except only including the function name and a description of what the function does. For example: 

/*

Function Name: FunctionName

Description: Blah blah blah.

*/

int FunctionName()

{

  code;

}

4.3 Inline Comments

Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code in that general area. Please use inline comments wherever the code might be confusing for others to understand.

4.4 Indent level

All documents must have indentation when writing code in a code block. The indent level in any case will consist of two spaces. There will be no tab use. For example: 

int someFunction

{

  code;

  more code;

}

4.5 Curly Bracket Use

Use of { } in a code block, such as in an if statement, a for loop, should start on a new line, with the { } lined up with the first character of the line above it. If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake. For example: 

if ( mapleLeafs == lose)

{

  fans->getAngry();

}

4.6 Variable Naming Conventions

Variables should follow regular programming conventions ( must start with lowercase letter, no symbols…). Variables should be descriptive for better understanding of it’s For example: 

int someVar;

4.7 Function Naming Conventions

Function names should start with a capital letter. For example: 

int SomeFunction()
{
  code;
}


ASOS Brigade
Last Name Name Seneca Username Section Blog Url IRC Nick Current Task SVN ID
Zhang Shun Yao syzhang4 C MY Blog DownWind IO_MenuBar 64
Hong Yong yhong17 B xDerick' Blog Yong_Clicker IO_Form, IO_Frame, IO_Field 65
Kim Taehoon tkim28 B Blog hoongoon IO_Radio 66
Chen Wen Fang wfchen C Gwen's Blog Gwen2009 IO_Label 62
Xue Yong yxue11 C Blog yxue11 IO_Edit,IO_Vedit 67
Tran Chi-Lea ctran13 C Nitty Gritty ctran13 ciol.c, IO_TextEdit 61
Tran Victor vvtran C Blog? victran IO_CheckList 63
Wang Cong cwang84 B Blog cwang84 IO_Menu 68
Contact: - - - - - - -
Tran Chi-Lea - - - - - -
Chen Wen Fang - - - - - - 
==
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OOP344_ASOS&oldid=30398"