OOP344 20131 Oopers

OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

Repository

+++ Git Repository ID: Ooper (https://github.com/Seneca-OOP344/8-Ooper.git) +++

Coding Guidelines

1) Software: Visual Studio 2010.

2) Blocking: Open and closed brackets {} should each be in a new line. Single syntax in functions are to be blocked as well.

Examples:

   if(whatever) do this; //bad

   if(whatever) 
      do this; // bad

   if(whatever)
   {
      do this:
   } // good

3) Identation: 3 spaces!

4) Variable Names:

• Private instance var - _dataExample - starts with underscore, first word is in lowercase, first letter of second word is uppercase (rest of characters are lowercase), etc.
• Public functions - GetData() - first letter of each word in function name is uppercase (rest of characters are lowercase).
• Each variable, when created, should be written in one line

Examples:

   int a; // good

   int a, b. c; //bad

5) Seneca Honesty Policy, Date, Professor Name, Student (or Group), Section, Class should be in a comment on the top of every source file (.cpp and .h)

Team Members

Email to all members

First Name	Last Name	Team Name	Section	Seneca Id	wiki id/Contributions	IRC nick	GITHUB ID	Blog URL
Peter	Huang	Oopers	B	phuang19	Peter Huang	phuang	peter-huang	Peter Huang's Blog
Mark	Hom	Oopers	B	mahom	Mark Hom	mahom	mahom21	OOP344 bLoG
Shay	Trotsky	Oopers	B	strotsky	Shay Trotsky	strotsky	strotsky	OOP344 Rules
Curtis	Wilson	Oopers	B	cjwilson3	Curtis Jordan Wilson	SL37	Curtis37	Curtis' Blog

Agenda

0.2 Milestone ((Due Thur Feb 14th, 23:59) )

Issue 2.0 - Create Oopers Wiki Site And Coding Standards

• Team wiki page

• Coding standards

Assigned to: Peter Huang

Issue 2.1 - Add console class to project 0.2 and test with cio_test

Assigned to:

Issue 2.2 - CLabel Mock-up Class

Assigned to:

Issue 2.3 - CDialog Mock-up Class

Assigned to:

Issue 2.4 - CLineEdit Mock-up Class

Assigned to:

Issue 2.5 - CButton Mock-up Class

Assigned to: Peter Huang