Changes

Jump to: navigation, search

OOP344 ASOS

1,896 bytes removed, 13:55, 20 November 2009
5.2 Channel #OOP344
[[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093 |OOP344 IRC Schedules]]<br />
=1.0 Project Overview = [[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093 |OOP344 IRC Schedules]]<br />
= 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 = == 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!
=== Chi-Lea Tran ===
Email: [mailto: ctran13@learn.senecac.on.ca === Wen Fang Chen === Email: wfchenctran13@learn.senecac.on.ca 2.2 Group Members Wen Fang Chen IRC Username: Gwen2009 Section: C Blog: http://wenfangchen.blogspot.com/]
Email: wfchen@learn== 2.senecac.on.ca2 Group Members ==
=== Yong Hong===
IRC Username: Yong_Clicker
Blog: http://xderick.blogspot.com/
Email: [mailto: rod1205@hotmail.comrod1205@hotmail.com]
Taehoon Kim IRC Username: hoongoon Section: B Blog: http://hoonkoon.blogspot.com/ Email: hoongoon86@hotmail.com === Chi-Lea Tran===
IRC Username: ctran13
Blog: http://ctran13.blogspot.com/
Email: [mailto: ctran13@learn.senecac.on.cactran13@learn.senecac.on.ca]
=== Victor Tran===
IRC Username: victran
Blog: http://victran.blogspot.com/
Email: [mailto: victor.vy.tran@gmail.comvictor.vy.tran@gmail.com]
 === Cong Wang===
IRC Username: cwang84
Blog: http://wangcong422.blogspot.com/
Email: [mailto: cwang84@learn.senecac.on.cacwang84@learn.senecac.on.ca]
Shun Yao Zhang=== Yong Xue ===
IRC Username: DownWindyxue11
Section: C
Blog: http://shunyaoopp344-cpayxue.blogspot.com/
Email: syzhang4[mailto:yxue11@learn.senecac.on.cayxue11@learn.senecac.on.ca]
Yong Xue== 2.3 Current responsiblities ==
IRC Username: yxue11=== Yong Hong ===
Section: CIO_Form, IO_Frame, IO_Field
Blog: http://opp344=== Chi-yxue.blogspot.com/Lea Tran ===
Email: yxue11@learn.senecac.on.caIO_TextEdit
=== Victor Tran ===
3.0 SVN RepositoryIO_CheckList
3.1 Address svn://zenit.senecac.on.ca/ops344_093a06 3.2 Usernames and Logins ===Cong Wang ===
4.0 Conventions and StylesIO_Menu
4.1 File headings=== Yong Xue ===
IO_Edit, IO_Vedit
Each file with the extension of *= 3.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:0 SVN =
== 3.1 Repository == svn://zenit.senecac.on.ca/ops344_093a06
/*== 3.2 Logins ==
File NameYong Hong: example.cppops344_093svn65
AuthorChi-Lea Tran: Victor Tran (victran)ops344_093svn61
DateVictor Tran: 27-Oct-09ops344_093svn63
DescriptionCong Wang: blah blah blahops344_093svn68
*/Yong Xue: ops344_093svn67
= 4.2 Function Comments0 Conventions and Styles =
== 4.1 File headings ==
Each function should file with the extension of *.cpp, *.c, and *.h must include a comment above the function similar to heading stating the file heading name, author (4.1and username), except only including the function name date created, last modified date, and a description of what the function 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>
== 4.2 Function Name: FunctionName Description: Blah blah blah.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:
<pre>
/*
* Function Name: FunctionName
* Description: Blah blah blah.
*/
int FunctionName()
 
{
}
</pre>
== 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 Inline comments should be used to clarify what exactly something is doing, or to leave a note for yourself or others regarding the code block. The indent level in any case will consist of two spacesthat general area. There will Please use inline comments wherever the code might be no tab useconfusing for others to understand. 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
 
{
}
</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: 
<pre>
if ( mapleLeafs == lose)
 
{
}
</pre>
== 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 letterIf the variable is a private or protected variable, no symbols…)use an _ before the variable name to differentiate from a public variable. Variables should be descriptive for better understanding of it’s For example:
<pre>
int someVar_someVar;
4.7 Function Naming Conventions</pre>
== 4.7 Function Naming Conventions ==
Function names should start with a capital 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
}SVN: ops344_093a06{| border="1" cellpadding="5".2 Channel #OOP344 ==
|+ [[ ASOS Brigade| ASOS Brigade]]! Last Name !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! Current Task !! SVN ID|November 11 -| Zhang || Shun Yao || syzhang4 || C || [http://shunyao-CPA.blogspot.com/ MY Blog] || DownWind || IO_MenuBar ||64|-| Hong || Yong || yhong17 || B || [http://xderick.blogspotmatrix.com/ xDerick' Blog] || Yong_Clicker || IO_Form, IO_Frame, IO_Field || 65|-| Kim || Taehoon || tkim28 || B || [http://hoonkoonsenecac.blogspoton.comca/ 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:/logfile/ctran13.blogspot.com Nitty Gritty] || ctran13 || ciol.c, IO_TextEdit|| 61|seneca-| Tran || Victor || vvtran || C || [http://victranoop344.blogspot.com Blog?] || victran || IO_CheckList || 63|-| Wang || Cong || cwang84 || B || [http:log<br //wangcong422.blogspot.com Blog] || cwang84 || IO_Menu || 68|-! Contact: !! - !! - !! - !! - !! - !! - !! -|-| Tran || Chi-Lea || - || - || - || - || - || -|-| Chen || Wen Fang || - || - || -|| - || -|| -|-|} ==>
1
edit

Navigation menu