Difference between revisions of "OOP344 ASOS"

From CDOT Wiki
Jump to: navigation, search
(ASOS Brigade - Team 6)
(5.2 Channel #OOP344)
 
(20 intermediate revisions by 4 users not shown)
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 />
+
= 1.0 Project Overview =
  
= ASOS Brigade - Team 6 =
+
== 1.1 Project Description ==                                                                                                                                                                                           
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 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.
 
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.
Line 41: Line 9:
 
== 1.2 Class Overview ==
 
== 1.2 Class Overview ==
  
 +
    This is incomplete!
  
  
Line 49: Line 18:
 
=== Chi-Lea Tran ===
 
=== Chi-Lea Tran ===
  
Email: ctran13@learn.senecac.on.ca
+
Email: [mailto:ctran13@learn.senecac.on.ca 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
+
== 2.2 Group Members ==
  
Yong Hong
+
=== Yong Hong ===
  
 
IRC Username: Yong_Clicker
 
IRC Username: Yong_Clicker
Line 75: Line 30:
 
Blog: http://xderick.blogspot.com/
 
Blog: http://xderick.blogspot.com/
  
Email: rod1205@hotmail.com
+
Email: [mailto:rod1205@hotmail.com rod1205@hotmail.com]
  
Taehoon Kim
+
=== Chi-Lea Tran ===
 
 
IRC Username: hoongoon
 
 
 
Section: B
 
 
 
Blog: http://hoonkoon.blogspot.com/
 
 
 
Email:                                                  hoongoon86@hotmail.com
 
 
 
Chi-Lea Tran
 
  
 
IRC Username: ctran13
 
IRC Username: ctran13
Line 95: Line 40:
 
Blog: http://ctran13.blogspot.com/
 
Blog: http://ctran13.blogspot.com/
  
Email: ctran13@learn.senecac.on.ca
+
Email: [mailto:ctran13@learn.senecac.on.ca ctran13@learn.senecac.on.ca]
  
Victor Tran
+
=== Victor Tran ===
  
 
IRC Username: victran
 
IRC Username: victran
Line 105: Line 50:
 
Blog: http://victran.blogspot.com/
 
Blog: http://victran.blogspot.com/
  
Email: victor.vy.tran@gmail.com
+
Email: [mailto:victor.vy.tran@gmail.com victor.vy.tran@gmail.com]
  
+
=== Cong Wang ===
 
 
Cong Wang
 
  
 
IRC Username: cwang84
 
IRC Username: cwang84
Line 117: Line 60:
 
Blog: http://wangcong422.blogspot.com/
 
Blog: http://wangcong422.blogspot.com/
  
Email: cwang84@learn.senecac.on.ca
+
Email: [mailto:cwang84@learn.senecac.on.ca cwang84@learn.senecac.on.ca]
  
Shun Yao Zhang
+
=== Yong Xue ===
  
IRC Username: DownWind
+
IRC Username: yxue11
  
 
Section: C
 
Section: C
  
Blog: http://shunyao-cpa.blogspot.com/
+
Blog: http://opp344-yxue.blogspot.com/
  
Email: syzhang4@learn.senecac.on.ca
+
Email: [mailto:yxue11@learn.senecac.on.ca yxue11@learn.senecac.on.ca]
  
Yong Xue
+
== 2.3 Current responsiblities ==
  
IRC Username: yxue11
+
=== Yong Hong ===
  
Section: C
+
IO_Form, IO_Frame, IO_Field
  
Blog: http://opp344-yxue.blogspot.com/
+
=== Chi-Lea Tran ===
  
Email: yxue11@learn.senecac.on.ca
+
IO_TextEdit
  
+
=== Victor Tran ===
 
  
3.0 SVN Repository
+
IO_CheckList
  
3.1 Address  svn://zenit.senecac.on.ca/ops344_093a06  3.2 Usernames and Logins   
+
===Cong Wang ===
 
  
4.0 Conventions and Styles
+
IO_Menu
  
4.1 File headings
+
=== Yong Xue ===
  
+
IO_Edit, IO_Vedit
  
                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:
+
= 3.0 SVN =
  
   
+
== 3.1 Repository == 
 +
    svn://zenit.senecac.on.ca/ops344_093a06  
  
/*
+
== 3.2 Logins ==
  
File Name: example.cpp
+
Yong Hong: ops344_093svn65
  
Author: Victor Tran (victran)
+
Chi-Lea Tran: ops344_093svn61
  
Date: 27-Oct-09
+
Victor Tran: ops344_093svn63
  
Description: blah blah blah
+
Cong Wang: ops344_093svn68
  
*/
+
Yong Xue: ops344_093svn67
  
4.2 Function Comments
+
= 4.0 Conventions and Styles =
  
+
== 4.1 File headings ==
  
                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 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>
 
/*
 
/*
 +
* File Name: example.cpp
 +
* Author: Victor Tran (victran)
 +
* Create Date: 27-Oct-09
 +
* Last Modified Date: 11-Nov-09
 +
* Description: blah blah blah
 +
*/
 +
</pre>
  
Function Name: FunctionName
+
== 4.2 Function Comments ==
 
 
Description: Blah blah blah.
 
  
*/
+
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>
 +
/*
 +
* Function Name: FunctionName
 +
* Description: Blah blah blah.
 +
*/
 
int FunctionName()
 
int FunctionName()
 
 
{
 
{
  
Line 192: Line 143:
  
 
}
 
}
 +
</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
 
 
 
 
  
                All documents must have indentation when writing code in a code block.  The indent level in any case will consist of two spacesThere will be no tab use. For example:
+
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 areaPlease 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:
 +
<pre>
 
int someFunction
 
int someFunction
 
 
{
 
{
  
Line 216: Line 161:
  
 
}
 
}
 +
</pre>
  
+
== 4.5 Curly Bracket Use ==
  
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:
 
 
 
 
 
                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 174:
  
 
}
 
}
 +
</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:
 +
<pre>
 +
int someVar;
 +
</pre>
  
                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:
+
If the variable is a private or protected variable, use an _ before the variable name to differentiate from a public variable.  For example:
  
   
+
  <pre>
  
int someVar;
+
int _someVar;
  
4.7 Function Naming Conventions
+
</pre>
  
             
+
== 4.7 Function Naming Conventions ==
  
Function names should start with a capital letter.  For example:
+
Function names should start with a lower letter.  For example:
  
+
<pre>
 +
int someFunction()
 +
{
 +
  code;
 +
}
 +
</pre>
  
int SomeFunction()
+
= 5.0 IRC Chatlogs =
  
{
+
== 5.1 Channel ##ASOS ==
 +
 
 +
October 27 - http://matrix.senecac.on.ca/~ctran13/logfile/Oct-27.log<br />
 +
November 11 - http://matrix.senecac.on.ca/~ctran13/logfile/Nov-11.log
  
  code;
+
*incomplete
  
}
+
== 5.2 Channel #OOP344 ==
SVN: ops344_093a06
 
{| border="1" cellpadding="5"
 
  
|+ [[ ASOS Brigade| ASOS Brigade]]
+
November 11 - http://matrix.senecac.on.ca/~ctran13/logfile/seneca-oop344.log<br />
! 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 || - || - || -|| - || -|| -
 
|-
 
|}
 
==
 

Latest revision as of 13:55, 20 November 2009

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

1.0 Project Overview

1.1 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

2.2 Group Members

Yong Hong

IRC Username: Yong_Clicker

Section: B

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

Email: rod1205@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

2.3 Current responsiblities

Yong Hong

IO_Form, IO_Frame, IO_Field

Chi-Lea Tran

IO_TextEdit

Victor Tran

IO_CheckList

Cong Wang

IO_Menu

Yong Xue

IO_Edit, IO_Vedit

3.0 SVN

3.1 Repository

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

3.2 Logins

Yong Hong: ops344_093svn65

Chi-Lea Tran: ops344_093svn61

Victor Tran: ops344_093svn63

Cong Wang: ops344_093svn68

Yong Xue: ops344_093svn67

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)
 * Create Date: 27-Oct-09
 * Last Modified Date: 11-Nov-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;

If the variable is a private or protected variable, use an _ before the variable name to differentiate from a public variable. For example:


int _someVar;

4.7 Function Naming Conventions

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

int someFunction()
{
  code;
}

5.0 IRC Chatlogs

5.1 Channel ##ASOS

October 27 - http://matrix.senecac.on.ca/~ctran13/logfile/Oct-27.log
November 11 - http://matrix.senecac.on.ca/~ctran13/logfile/Nov-11.log

  • incomplete

5.2 Channel #OOP344

November 11 - http://matrix.senecac.on.ca/~ctran13/logfile/seneca-oop344.log