== <big>Team Members </big> ==

|+ OOP344 - 2010 Team !YOU-  [mailto:mdadams1@learn.senecac.on.ca,mddaniels@learn.senecac.on.ca,fmdeoliveira@learn.senecac.on.ca,ammisko@learn.senecac.on.ca,amward1@learn.senecac.on.ca,mziaei1@learn.senecac.on.ca,nsimmalavong@learn.senecac.on.ca,tjcatibog@learn.senecac.on.ca Email All]

| (A)Adams|| [http://zenit.senecac.on.ca/wiki/index.php/User:Mdadams1 Matthew]|| [mailto:mdadams1@learn.senecac.on.ca mdadams1]|| A || http://www.tandemwebdesign.ca/blog || MattAdams|| [[Special:Contributions/mdadams1 | Contributions]]

| (A)Catibog|| [http://zenit.senecac.on.ca/wiki/index.php/User:Tjcatibog Timothy]|| [mailto:tjcatibog@learn.senecac.on.ca tjcatibog]|| A|| http://tjprogramming.blogspot.com/ || tjcatibog|| [[Special:Contributions/tjcatibog | Contributions]]

| (A)De Oliveira|| [http://zenit.senecac.on.ca/wiki/index.php/User:fmdeoliveira Felipe]|| [mailto:fmdeoliveira@learn.senecac.on.ca fmdeoliveira]|| A || http://feliploko.wordpress.com/ || fmDeOliveira || [[Special:Contributions/fmdeoliveira | Contributions]]

| (A)Misko|| [http://zenit.senecac.on.ca/wiki/index.php/User:ammisko Andrew]|| [mailto:ammisko@learn.senecac.on.ca ammisko]|| A || http://ammisko.blogspot.com || ammisko || [[Special:Contributions/ammisko | Contributions]]

| (A)Ward|| [http://zenit.senecac.on.ca/wiki/index.php/User:Amward1 Amy]|| [mailto:amward1@learn.senecac.on.ca amward1]|| A || http://amward1.wordpress.com/ || award|| [[Special:Contributions/amward1 | Contributions]]

| (A)Ziaei|| [http://zenit.senecac.on.ca/wiki/index.php/User:Mziaei1 Minoo] || [mailto:mziaei1@learn.senecac.on.ca mziaei1]|| A || http://minooz.wordpress.com/ || Minooz || [[Special:Contributions/mziaei1 | Contributions]]

==<big>Skype</big> = IRC Meetings = {| class="wikitable sortable" border="1" cellpadding="5"We need to decide when we should have our meetings.|+ Skype Name

{! Name !! SkyName |-| Matthew Adams || matt_adams21|-| Amy Ward || AmyWard11|-| Minoo Ziaei || class="wikitable" border="1"mziaei53|+ Discussion-! Name !! Comment| Timothy Catibog || jordyy.catibog

| fmDeOliveira Felipe de Oliveira || Evenings work better for me... It is hard to find some time in the morning or afternoon that all or most of us are able to be on IRC.feliploko

| ammisko Andrew Misko || Evening are also good for me. I don't have class later than 320 every day. As long as I know a few days in advance I shouldn't have a problem with meeting any time after 320.ammisko

== Team Programming Standards <big>IRC</big> ==An area for listing our teams programming standards that we will use when constructing the projectOur IRC channel is #oop344_!you on freenode. Please follow these rules when writing code for this project. This will make it easier for us to help each other and collaborate in join the whole processchannel whenever you are on IRC.

=== Declare only one variable in each line. ===This makes it easier The channel is restricted to scan Fardad and the code team members. There is an access list that will automatically kick and find ban anyone not listed. For this reason, we should always make sure we are using our official IRC nicks (or one within our nick group) and that we are identified with the type of a variable that you see somewhere else in nickserv (/nickserv identify ''mypassword'') before issuing the codejoin command.

Do: int If you are getting a; int b = 0; int c = a;message that you are banned on our channel, make sure you are identified and then issue the command

Don't: int a, b = 0, c = a;/chanserv unban #oop344_!you

=== Do not use tabs when indenting[http://zenit. senecac.on.ca/wiki/index.php/Team_!YOU_-_IRC_Meetings IRC Meetings] ===The tab space is interpreted different across different software and operating systemsOur first meeting was on Wednesday, January 27th, from 10pm to midnight. Use normal spaces On the following weeks, we will meet regularly on Mondays from 8pm to add indentation instead10pm.

==== (Discussion: Indentation) ==<big>Team Programming Standards</big> ==Something simple, but An area for listing our teams programming standards that should be standard we will use when constructing the project. Please follow these rules when writing code for this project. This will make it easier for all pieces of us to help each other and collaborate in the codewhole process.

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I usually put two spaces for To view a new indent, and keep a blank line between new big blocks list of code and whatever comes before it (usually an if statementour agreeded upon programming standards, a for loop, or the signature of a function)please visit [http://zenit.senecac.on.ca/wiki/index.|php/Team_!YOU_-| MattAdams || Please only indent to 4 spaces_Official_Standards http://zenit. If we all use the same indenting, when it comes to putting our code together it will looks the samesenecac.on.NOTE: Most text editors have the option to change tabs to spaces, so you are still able to press the tab key, however it will convert it to spaces when the file is savedca/wiki/index.|php/Team_!YOU_-|}_Official_Standards].

=== (Discussion: Use of iterating variables on for loops) [[Team !YOU - BIO Library | Basic Input Output Library]] ===There are two major ways of dealing with the iteration variable on '''for''' loops. We should come to a consensus on how to deal with it on our project.

Option 1: Declare Our page for the variables outside the loop; initialize them inside basic input output library, the loop; keep their exit values for future use. int i; // counter for (i = 0; i<5; i++) printf("."); // Prints ...first part of our project.. printf("%d",i); // Prints 5

Option 2: Declare and initialize variables inside the loop; lose the variable at the end of the loop scope; for (int i = 0; i<5; i++) printf("."); // Once the loop is done, variable i cannot be accessed anymore.== [[!You's OpText - OOP344 | OpText]] ===

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I definitely prefer option 2. It is much easier to keep recycling the loop variables without having to worry if they already exist or not==Part1: [http://zenit. In case we need the value of the loop variable after the loop is done, we should just copy it to another variable before the end of the loopsenecac.|-| ammisko || I like option 1 better (I changed it a bit)on. I think it looks cleaner and is much easier to read for someone who doesn't know what the code does (especially with comments)ca/wiki/index. Also what if we need to use a loop variable from outside the for loop? Or if we need to use the first part of the forphp/Create_Class_Prototypes_-loop for other code? Option 1 could accommodate that better I think.|_!You_-_OOP344 Create Class Prototypes]====

| MattAdams || I like both ways====Part2: [http://zenit. I use option1 when I need to use the counter for something elsesenecac. And I use option2 when I need to right a quick for loopon. As for a standard, I think option1 should be used, that way all of the variables are declared at the top of every function, and that way we don't have to copy the counter to another variableca/wiki/index. |php/Code_all_member_functions_-_!You_-|} _OOP3444 Code all member functions]=== (Discussion: Variable names) ===How should we name the variables that we create on our project?

{! Tasks | class="wikitable" border="1"|+ DiscussionMembers Working On It !! Name Status !! CommentDue Date

| fmDeOliveira BForm::edit ||MattAdams | I suggest we avoid abbreviations, since what might be obvious for some could be confusing for others. Full words or short expressions could be used where the first letter is always lower case, and the first letter of the following words are upper case. Examples: cost, totalPrice, numberOfPeople.| In Progress || -

 | MattAdams BForm Constructor/Destructor || Minoo || committed || I also agree w/ Felipe. Using Camle notation is a nice and easy way to name variables. HoweverMarch 23, I would have said numOfPeople, instead of 'numberOfPeople'. As for #define goes. Use UPPER case, and separate words by the underscore(_). ie. #define ISBN_LENGTH, #define AREA_MAX, #define MAX, #define LENGTH2010 midnight|}-  === (Discussion| BForm:: Use of comments) ===When should we use double slash display(//) and when should we use slash-asterisk (/* */)?  {| class="wikitable" border="1"|+ Discussion! Name !! CommentAmy || committed || March 23, 2010 midnight

| fmDeOliveira BForm::add() x2 || I prefer using // for single-line comments and /* */ for blocks of commented code. This would avoid problems commenting out blocks of code that already have single-line comments (the end of the single-line comment would not be interpreted as the end of the block comment).Timothy |- | MattAdams committed || I also like using // for end of the line comments to slitly explain whats going on, and use /* */ for commented out codeMarch 23, as well as explaining a certain block of code that is confusing to understand.2010 midnight

=== (Discussion: Nesting) =<big>Helpful External Links</big> ==How do we deal with else statements? Option 1: else right after the end of the if block if (a > 0) { printf("."); } else { printf(","); } Option 2: else on a line below the end of the if block if (a > 0) { printf("."); } else { printf(","); }

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I prefer option 2[http://www.|- | MattAdams || Option 2 all the waymicrosoft. |-|}com/express/Downloads/ Microsoft Visual Studio Express Edition Download]