== <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]]

== IRC <big>Skype</big> ==Our IRC channel is #oop344_!you on freenode. Please join the channel whenever you are on IRC.

{| class="wikitable sortable" border="1" cellpadding= IRC Meetings ==="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 ==An area for listing If you are getting a message that you are banned on our teams programming standards that we will use when constructing the project. Please follow these rules when writing code for this project. This will channel, make it easier for us to help each other sure you are identified and collaborate in then issue the whole process.command

=== Declare only one variable in each line. ===This makes it easier to scan the code and find the type of a variable that /chanserv unban #oop344_!you see somewhere else in the code.

Don't=== [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_IRC_Meetings IRC Meetings] === int aOur first meeting was on Wednesday, January 27th, b = 0from 10pm to midnight. On the following weeks, c = a;we will meet regularly on Mondays from 8pm to 10pm.

==<big>Team Programming Standards</big> = Do not =An area for listing our teams programming standards that we will use tabs when indentingconstructing the project. ===The tab space is interpreted different across different software and operating systemsPlease follow these rules when writing code for this project. Use normal spaces This will make it easier for us to add indentation insteadhelp each other and collaborate in the whole process.

=== Put the pointer identifier(*) right after the target variable typeTo view a list of our agreeded upon programming standards, please visit [http://zenit. ===Pointers are hard enough to deal withsenecac. It only makes it more complicated if they are declared differently throughout the codeon.ca/wiki/index.php/Team_!YOU_-_Official_Standards http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards].

==<big>The Project</big> = (Discussion: Use of iterating variables on for loops) ===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 the variables outside the loop; initialize them inside the loop; keep their exit values An area for future use. int i; // counter us to post information and links for (i = 0; i<5; i++) printf("."); // Prints ....our team 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.== [[Team !YOU - BIO Library | Basic Input Output Library]] ===

{| 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. In case we need the value of Our page for the loop variable after the loop is donebasic input output library, we should just copy it to another variable before the end of the loop.|-| ammisko || I like option 1 better (I changed it a bit). I think it looks cleaner and is much easier to read for someone who doesn't know what the code does (especially with comments). 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 for-loop for other code? Option 1 could accommodate that better I thinkour project.|-|}

=== (Discussion=Part1: Variable names) [http://zenit.senecac.on.ca/wiki/index.php/Create_Class_Prototypes_-_!You_-_OOP344 Create Class Prototypes]====How should we name the variables that we create on our project?

|+ DiscussionClass Member Functions ! Tasks || Members 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 || -

|}BForm Constructor/Destructor || Minoo || committed || March 23, 2010 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 || Timothy || committed || 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).March 23, 2010 midnight

=== (Discussion[http: Indentation) ===Something simple, but that should be standard for all pieces of the code//www.  {| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I usually put two spaces for a new indent, and keep a blank line between new big blocks of code and whatever comes before it (usually an if statement, a for loop, or the signature of a function)microsoft.|-|}com/express/Downloads/ Microsoft Visual Studio Express Edition Download]