Team I - OOP344 20133

Team Infinity

EMAIL US

Project Marking Percentage

Group work:      50%     
Individual work: 50% +   
-------------------------
Total           100%

Repository

• Team Infinity Repo Path: https://github.com/Seneca-OOP344/Team-I

Team Members

Team Infinity

First Name	Last Name	Section	Seneca Id	wiki id	IRC nick	Blog URL
Deval	Patel	C	drpatel17	Deval Rameshbhai Patel	Mario1005	[1]
Kamleshkumar	Korat	C	kjkorat	Kamleshkumar Jayantibhai Korat	Maverick344	[2]
Kashyap	Patel	C	kbpatel13	Kashyap Babubhai Patel	H3ll0W0rld	[3]
Zhenyang	Chen	A	zchen91	Zhenyang Chen	crans	[4]

Tasks

The Application

Mandatory

1. Browse Record   Complete
   • Member: Kamlesh Korat, Deval Patel, Zhenyang Chen, Kashyap Patel
2. Append Empty Record   Complete
   • Member: Kamlesh Korat, Deval Patel, Zhenyang Chen
3. Edit Record
   • Member:

Optional

1. Search Record
   • Member:
2. Delete Record
   • Member:

Release 0.4

1. CButton - 25%   Complete
   • Member: Kamlesh Korat
2. CCheckMark - 25%   Complete
   • Member: Deval Patel
3. CValEdit - 25%   Complete
   • Member: Kashyap Patel
4. CMenuItem - 25%   Complete
   • Member: Zhenyang Chen

Release 0.3 is due Nov 4th, 23:59

1. Prototyping - 16%   Complete
   • Member: Zhenyang Chen
2. CLabel - 17%   Complete
   • Member: Kamlesh Korat
3. CDialog - 50%   Complete
   • Member: Deval Patel and Zhenyang Chen
4. CLineEdit - 17%   Complete
   • Member: Kashyap Patel

Release 0.2 is due October 20th, 23:59

1. Organize and complete team page - by Deval Patel, Kamlesh Korat, Zhenyang Chen, Kashyap Patel
2. Select a team member's console.cpp and console.h to use - by Zhenyang Chen
   • That team member should branch and clone repository and add the files to it as well as comment on cframe.h with github id, date, and time and merge it back
3. All other members clone the repository, comment, and test the execution of CFrame - by Kamlesh Korat, Deval Patel, Kashyap Patel
   • The comment should include your github id, date, and time in the cframe.h file
   • Push the final changes to github

Coding Style and Standards

• The following will serve as an example of our coding standard:

#ifndef __TEAMINFINITY_FILENAME_H__ // Our Team's Safeguard
#define __TEAMINFINITY_FILENAME_H__


class example { // There will be a space after every class identifier for the definition
  public:
  int _data; // Member variables should start with an underscore
  int _arraySize // Use meaningful names for variables when applicable and use lower Camel Case
  int _width; // Every object have its own type
  char* _pArray; // Pointers should have * part of the type
  void display():
};

void example::display() { // There will be a space after every function identifier for the definition 
}

#endif

...

#include <iostream>
#include <cstring>
using namespace std;

int main() {
  int a = 0; // Indentation is 2 spaces
  int b = 1; // NO Tab characters allowed! Replace every tab character with 2 spaces.
  char name[] = "Spoom";
  // Put a newline after variable declaration
  if(a > b ? a : b) {
  a = a * b; // Put a space between EVERY variable and operator
  }
  // Put a newline after a control structure
  if(!strcmp(name, "Spoom")) {
  cout << "Welcome, Spoom!" << endl; // Every statement within a control structure will
  } // be wrapped in braces, even if there is only 1 line
  else { // Else statement will be on a newline after the If control structure
  cout << "Get out." << endl;
  }

  return 0;
}
Courtesy:Team B