Changes

== ASOS Brigade ==SVN: ops344_093a06{| border="1" cellpadding.0 Project Overview ="5"

|== 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: [[ ASOS Brigade| ASOS Brigade]mailto:ctran13@learn.senecac.on.ca ctran13@learn.senecac.on.ca]! Last Name !! Name !! Seneca == 2.2 Group Members == === Yong Hong === IRC Username !! : Yong_Clicker Section !! Blog Url !! IRC Nick !! Current Task !! SVN ID: B|-| Zhang || Shun Yao || syzhang4 || C || [Blog: http://shunyao-CPAxderick.blogspot.com/ MY Blog Email: [mailto:rod1205@hotmail.com rod1205@hotmail.com] || DownWind || IO_MenuBar ||64|=== Chi-Lea Tran === IRC Username: ctran13 Section: C | Hong || Yong || yhong17 || B || [Blog: http://xderickctran13.blogspot.com/ xDerick' Blog Email: [mailto:ctran13@learn.senecac.on.ca ctran13@learn.senecac.on.ca] || Yong_Clicker || IO_Form, IO_Frame, IO_Field || 65|-| Kim || Taehoon || tkim28 || B || [=== Victor Tran === IRC Username: victran Section: C Blog: http://hoonkoonvictran.blogspot.com/ Blog Email: [mailto:victor.vy.tran@gmail.com victor.vy.tran@gmail.com] || hoongoon || IO_Radio || 66|-| Chen || Wen Fang || wfchen || C || [=== Cong Wang === IRC Username: cwang84 Section: B Blog: http://wenfangchenwangcong422.blogspot.com/ Gwen's Blog Email: [mailto:cwang84@learn.senecac.on.ca cwang84@learn.senecac.on.ca] || Gwen2009 || IO_Label || 62|-| === Yong Xue || Yong || === IRC Username: yxue11 ||  Section: C || [ Blog: http://opp344-yxue.blogspot.com/ Blog Email: [mailto:yxue11@learn.senecac.on.ca yxue11@learn.senecac.on.ca] || yxue11 || IO_Edit == 2.3 Current responsiblities == === Yong Hong === IO_Form, IO_Frame,IO_Vedit|| 67IO_Field|-| Tran || === Chi-Lea || ctran13 || C || [httpTran === IO_TextEdit === Victor Tran === IO_CheckList ===Cong Wang === IO_Menu === Yong Xue === IO_Edit, IO_Vedit = 3.0 SVN = == 3.1 Repository == svn://ctran13zenit.senecac.blogspoton.com Nitty Gritty] || ctran13 || ciolca/ops344_093a06  == 3.c, IO_TextEdit|| 612 Logins == Yong Hong: ops344_093svn65 |Chi-Lea Tran: ops344_093svn61| Victor Tran || Victor || vvtran || C || [http: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 */victran.blogspot For example:  <pre>/* * File Name: example.com Blog?] || cpp * Author: Victor Tran (victran || IO_CheckList ) || 63* Create Date: 27-Oct-09| * Last Modified Date: 11-Nov-09 * Description: blah blah blah */</pre> == 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: <pre>/* * Function Name: FunctionName| Wang || Cong || cwang84 || B || [http * Description:Blah blah blah. */int FunctionName(){  code; }</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 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{  code;  more code; }</wangcong422pre> == 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.blogspot If the code block only has one coded line for the result, please use the curly brackets anyways for readability’s sake.com Blog] || cwang84 || IO_Menu || 68For example: <pre>if ( mapleLeafs == lose)|{  fans->getAngry(); }</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>! ContactIf the variable is a private or protected variable, use an _ before the variable name to differentiate from a public variable. For example: !! - !! - !! - !! - !! - !! - !! -|-| Tran || Chi-Lea || - || - || - || - || - || -<pre> int _someVar; </pre> == 4.7 Function Naming Conventions == Function names should start with a lower letter. For example: <pre>int someFunction(){ code;}</pre> = 5.0 IRC Chatlogs = == 5.1 Channel ##ASOS ==|-| Chen || Wen Fang || 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 *incomplete == 5.2 Channel #OOP344 == November 11 -|| http://matrix.senecac.on.ca/~ctran13/logfile/seneca-|-|}oop344.log<br />