Difference between revisions of "OOP344 - Success - 20102"
(→Rules to follow: minor) |
(→IRC meetings: Added table of awailable time for IRC meetings) |
||
Line 10: | Line 10: | ||
[[OOP344 - Success IRC Logs - 20102 | IRC meeting logs]] | [[OOP344 - Success IRC Logs - 20102 | IRC meeting logs]] | ||
<p>Freenode channel : #OOP344Success</p> | <p>Freenode channel : #OOP344Success</p> | ||
+ | |||
+ | Please mark time in this table when you are usually awailable for IRC meetings. | ||
+ | |||
+ | {| border="1" cellpadding="5" | ||
+ | |||
+ | ! - !! SUN<br /> !! MON<br /> !! TUE<br /> !! WED<br /> !! THU<br /> !! FRI<br /> !! SAT<br /> | ||
+ | |- | ||
+ | | 09:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 10:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 11:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 12:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 13:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 14:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 15:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 16:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 17:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 18:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 19:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | | 20:00 || - || - || - || - || - || - || - | ||
+ | |- | ||
+ | |} | ||
== Member List == | == Member List == |
Revision as of 23:54, 26 May 2010
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Team Success
Short link for our team page: bit.ly/s_ss
Project Development
IRC meetings
Freenode channel : #OOP344Success
Please mark time in this table when you are usually awailable for IRC meetings.
- | SUN |
MON |
TUE |
WED |
THU |
FRI |
SAT |
---|---|---|---|---|---|---|---|
09:00 | - | - | - | - | - | - | - |
10:00 | - | - | - | - | - | - | - |
11:00 | - | - | - | - | - | - | - |
12:00 | - | - | - | - | - | - | - |
13:00 | - | - | - | - | - | - | - |
14:00 | - | - | - | - | - | - | - |
15:00 | - | - | - | - | - | - | - |
16:00 | - | - | - | - | - | - | - |
17:00 | - | - | - | - | - | - | - |
18:00 | - | - | - | - | - | - | - |
19:00 | - | - | - | - | - | - | - |
20:00 | - | - | - | - | - | - | - |
Member List
ID | Last Name | Name | Seneca Username | Section | Blog Url | IRC Nick | SVN ID | My Contributions | Role |
---|---|---|---|---|---|---|---|---|---|
A | Pliats | Aleh | apliats | A | http://oleg-oop.blogspot.com/ | oleg_pliats | n/a | Contributions | |
B | Quan | Jason | jquan4 | A | http://jasonquan.wordpress.com/ | JQuan | n/a | Contributions | |
C | Schranz | Matthew | mjschranz | A | OOP344 Blog Posts | mjschranz | n/a | Contributions | |
D | Balzamova | Irina | ibalzamova | A | http://bikarin.blogspot.com/ | iIra | n/a | Contributions | |
E | Park | Hong Geung | hgpark | A | http://goldenration.wordpress.com/ | goldenration | n/a | Contributions |
Rules to follow
(this is just an example, lets discuss it)
1. Two spaces for indentation
example:
int main { int i; int j; if (i == 0) { i = 1; } }
2. Name variables like this: char myVariable; int tempSize (first letter is small);
3. Do not create variables that are never use
4. Only use breaks in switch statements
5. Begin each class with #ifndef (we will learn it later)
6. Do not use redundant statements (i.e: if (x != 0) because it same as if(x) )
7. Very important - we shouldn't use TAB for indention.
Because size of tab is different in different compilers and code could look messy
if to open it different compiler. Lets use space instead.
And each of us should set up Visual Studio to turn off TAB otherwise we can lose marks.
Note from Matthew: Look into the program you are writing on to see if you can set the number of characters your tab key will indent. For myself, I write all of my code on an application called SubEtheEdit on my mac and I can set my tab to the 2 characters we specified, so I can easily still use tab personally.
Aleh: In VisualStudio we can put settings like here and by pressing TAB spaces would be printed. I will ask Fardad if it is ok.
8. Do not create several variables in one line
int a,b; //BAD
int a; //GOOD
int b; //GOOD