Open main menu

CDOT Wiki β

Changes

Team !YOU - OOP344

1,455 bytes removed, 21:15, 30 March 2010
m
adding name to skype list
{{OOP344 Index}}
This is Team !YOU's Project Page
== <big>Team Members </big> ==
{| class="wikitable sortable" border="1" cellpadding="5"
|+ 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]
! Last Name !! Name !! Seneca ID !! Section !! Blog URL !! IRC nick !! My Contributions
|-
| (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]]
|-
| Daniels|| [http://zenit.senecac.on.ca/wiki/index.php/User:Mddaniels Matthew]|| [mailto:mddaniels@learn.senecac.on.ca?subject=OOP344 mddaniels]|| A || http://cdnpadawan.wordpress.com/ || CDNPadawan || [[Special:Contributions/mddaniels | 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]]
|-
| Simmalavong|| [http://zenit.senecac.on.ca/wiki/index.php/User:nsimmalavong Niki]|| [mailto:nsimmalavong@learn.senecac.on.ca nsimmalavong]|| A || http://oop344-niki.blogspot.com/ || nsimmalavong || [[Special:Contributions/nsimmalavong | 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>Discussions</big> ==
Please visit the [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Discussions Discussion Page] often, so we can share resources and opinions with others in between our weekly meetings.
== IRC ==
Our IRC channel is #oop344_!you on freenode. Please join the channel whenever you are on IRC.
==<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
|-
 
|}
== <big>IRC</big> ==
Our IRC channel is #oop344_!you on freenode. Please join the channel whenever you are on IRC.
== Team Programming Standards ==An area for listing our teams programming standards The channel is restricted to Fardad and the team members. There is an access list that we will use when constructing the projectautomatically kick and ban anyone not listed. Please follow these rules when writing code for For this project. This will reason, we should always make it easier for us to help each other sure we are using our official IRC nicks (or one within our nick group) and collaborate in that we are identified with the nickserv (/nickserv identify ''mypassword'') before issuing the whole processjoin command.
=== Declare only one variable in each line. ===This makes it easier to scan the code and find the type of If you are getting a variable message that you see somewhere else in are banned on our channel, make sure you are identified and then issue the code.command
Do: int a; int b = 0; int c = a;/chanserv unban #oop344_!you
Don't: int a, b = 0, c = a;before trying to join again.
=== [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_IRC_Meetings IRC Meetings] ===
Our first meeting was on Wednesday, January 27th, from 10pm to midnight. On the following weeks, we will meet regularly on Mondays from 8pm to 10pm.
=== Do not use tabs when indentingTo view information about past or upcoming meetings, please visit [http://zenit. ===The tab space is interpreted different across different software and operating systemssenecac. Use normal spaces to add indentation insteadon.<br ca/><br wiki/>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 savedindex.php/Team_!YOU_-_IRC_Meetings http://zenit.senecac.on.<br ca/><br wiki/>Should we declare an indent spacing rule? As in, only use 3 spaced, or 4 spacesindex. That way all of our code is indented equally? I think that 3 or 4 spaces is okay, anything more than that just takes up to much roomphp/Team_!YOU_-_IRC_Meetings].
==<big>Team Programming Standards</big> = Put the pointer identifier(*) right after =An area for listing our teams programming standards that we will use when constructing the target variable typeproject. ===Pointers are hard enough to deal withPlease follow these rules when writing code for this project. It only makes This will make it more complicated if they are declared differently throughout easier for us to help each other and collaborate in the codewhole process.
Do=== [http: int* p1; char* p2;//zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards Official Team !You Programming Standards] ===
Don'tTo view a list of our agreeded upon programming standards, please visit [http: int *p1; char *p2;//zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards].
=== (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 for future use.
int i; // counter
for (i = 0; i<5; i++) printf("."); // Prints .....
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= <big>The Project<5; i++) printf("."); // Once the loop is done, variable i cannot be accessed anymore.big> ==
{| 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 An area for us to worry if they already exist or not. 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 loop.|-| ammisko || I like option 1 better (I changed it a bit). I think it looks cleaner post information 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 links for other code? Option 1 could accommodate that better I thinkour team project.|-|}
=== [[Team !YOU - BIO Library | Basic Input Output Library]] ===
=== (Discussion: Variable names) ===How should we name Our page for the variables that we create on basic input output library, the first part of our project?.
=== [[!You's OpText - OOP344 | OpText]] ===
{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I suggest we avoid abbreviations, since what might be obvious for some could be confusing for others==Part1: [http://zenit.senecac. 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 caseon. Examples: cost, totalPrice, numberOfPeopleca/wiki/index.|php/Create_Class_Prototypes_-_!You_-|}_OOP344 Create Class Prototypes]====
====Part2: [http://zenit.senecac.on.ca/wiki/index.php/Code_all_member_functions_-_!You_-_OOP3444 Code all member functions]====
=== (Discussion=Part3: Use of comments) Code BForm functions===={| class="wikitable" border="1"When should we use double slash (//) and when should we use slash-asterisk (/* */)?|+ Class Member Functions
 {! Tasks | class="wikitable" border="1"|+ DiscussionMembers Working On It !! Name Status !! CommentDue Date
|-
| fmDeOliveira BForm::edit || MattAdams || In Progress || 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).
|-
|}BForm Constructor/Destructor || Minoo || committed || March 23, 2010 midnight|-  === | BForm::display(Discussion: Indentation) ===Something simple, but that should be standard for all pieces of the code.  {| class="wikitable" border="1"|+ Discussion! Name !! CommentAmy || committed || March 23, 2010 midnight
|-
| fmDeOliveira BForm::add() x2 || Timothy || committed || I usually put two spaces for a new indentMarch 23, 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).2010 midnight
|-
| BForm::editable, fieldNum, curField, operator[] || Felipe || committed || March 23, 2010 midnight
|}
== <big>Helpful External Links</big> ==
=== (Discussion[http: Nesting) ===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//www.|- | MattAdams || Option 2 all the waymicrosoft|-|}com/express/Downloads/ Microsoft Visual Studio Express Edition Download]
1
edit