21
edits
Changes
Created page with '=0.2 Milestone= == Create a Team page == * create a team page with following format for the name: *: '''''OOP344 20131 - Team Name''''' * Your team page must have the following i…'
=0.2 Milestone=
== Create a Team page ==
* create a team page with following format for the name:
*: '''''OOP344 20131 - Team Name'''''
* Your team page must have the following information:
*: Team members and their Full contact information
*: Programming Style to be followed by the team during project implementation. (see next section)
*: Any other information needed to be discussed and announced for the project.
== Common Style ==
*Talk with you team mates and come up with ONE STYLE to work with.
*This style includes at least the following three aspects:
*# Indentation
*# Blocks
*# Variable Naming.
*Add the style to the team page
== Start Working==
'''''Make sure all your branch names follow the specs stated in the project description'''''<br />
'''''Make sure an issue is created for each task before branching is done'''''<br />
'''''Do not forget to repeatedly and consistantly commit your code and push back to the repository'''''
* Adding Your console class to the project
*# Select one of the Console classes, done by one of the team members
*# S/he should branch the repository using a proper name.
*# Switch to the branch and add the console class to the project
*# compile and test it with cio_test.cpp (the latest version) and Test1Frame.cpp
*# Do a final push to GitHub
*# Issue a pull request and let one of the team-mates to confirm the style and performance
*# Merge back to repo
* Mockups
*# Each team member will pick a class, create an issue and branch the master repo to start
*# S/he will swicth to the branch and create two files using the same name as the picked class(all lowercase)
*# Class declaration is added to the header file from the description of the assignment (don't forget safegaurds)
*# Class implementation will be added to the cpp file
*#* Class implementation includes blank constructors, destructors an bland methods for all non-pure virtual methods of the class.
*#* make sure constructors properly '''''initialize''''' the Base class
*# Compile the newly added class '''''ONLY'''' (cpp file)
*# Do a final push to GitHub
*# Issue a pull request assigned to another team-mate
*# After confirmation of compilation (no warnings), style and initialization logic, branched is merged back to master by either the developer or the code-reviewer.
== Create a Team page ==
* create a team page with following format for the name:
*: '''''OOP344 20131 - Team Name'''''
* Your team page must have the following information:
*: Team members and their Full contact information
*: Programming Style to be followed by the team during project implementation. (see next section)
*: Any other information needed to be discussed and announced for the project.
== Common Style ==
*Talk with you team mates and come up with ONE STYLE to work with.
*This style includes at least the following three aspects:
*# Indentation
*# Blocks
*# Variable Naming.
*Add the style to the team page
== Start Working==
'''''Make sure all your branch names follow the specs stated in the project description'''''<br />
'''''Make sure an issue is created for each task before branching is done'''''<br />
'''''Do not forget to repeatedly and consistantly commit your code and push back to the repository'''''
* Adding Your console class to the project
*# Select one of the Console classes, done by one of the team members
*# S/he should branch the repository using a proper name.
*# Switch to the branch and add the console class to the project
*# compile and test it with cio_test.cpp (the latest version) and Test1Frame.cpp
*# Do a final push to GitHub
*# Issue a pull request and let one of the team-mates to confirm the style and performance
*# Merge back to repo
* Mockups
*# Each team member will pick a class, create an issue and branch the master repo to start
*# S/he will swicth to the branch and create two files using the same name as the picked class(all lowercase)
*# Class declaration is added to the header file from the description of the assignment (don't forget safegaurds)
*# Class implementation will be added to the cpp file
*#* Class implementation includes blank constructors, destructors an bland methods for all non-pure virtual methods of the class.
*#* make sure constructors properly '''''initialize''''' the Base class
*# Compile the newly added class '''''ONLY'''' (cpp file)
*# Do a final push to GitHub
*# Issue a pull request assigned to another team-mate
*# After confirmation of compilation (no warnings), style and initialization logic, branched is merged back to master by either the developer or the code-reviewer.
