|October 28November 3

|November 1830

* [https://cs.senecac.on.ca/~btp300/pages/assignments/a2.html Field Frame Classes] - Coded and Submitted as a Group * Each game is a team effort. The structure of each team is up to the team members. Each member must contribute their own work in a selected area or areas of their choosing. Before continuing stage 2, please do the following# Read [[Hints for Using SVN to collaborate on school projects]]# Update your team's wiki page with your team's repository path information under '''Repo Path'''# Create a directory with your seneca id under the branch sub-directory of your team's repository. This will be your home directory for development; for details see: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Directory_Structure Directory Structure] <!--# One of your team members should export svn://zenit.senecac.on.ca/btp300_113/trunk into the trunk of your team's repository#: For detailed steps see [[Hints for Using SVN to collaborate on school projects#Start_the_project_by_continuing_an_existing_work | Start the project by continuing an existing work]] Each team member should have their own successfully compiled version of the assignment 1 in their own workspace in the branch sub-directory of their team's repository.Branch submission path: svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment1 : ''Start doing the above by branching the Framework into svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment2. See here for help: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Preparing_Branches.2Fworkspace_for_development Preparing Branches/workspace for development]''  The source code for the upgraded sample should include the following updates:* your own name in the caption for the dialog box* your team name in the window title 

Merge all of Before starting stage 2, read [[Hints for Using SVN to collaborate on school projects]] and do the following:# Update your team members' Framework workspaces back s wiki page with your team's repository path under '''Repo Path'''# Add assignment 1 to the trunk so that of your team's repository as follows## Checkout your team's empty repository to a new directory on a local computer## Create the caption of branches, tags, and trunk subdirectories under this new directory## Under the dialog box shows all of branches subdirectory create a sub-subdirectory for each team member using their seneca id## Under the names sub-subdirectory for one of the team memberscreate a new sub-sub-subdirectory named '''assignment_1'''##* You can do this manually or by creating a new Visual Studio solution named '''assignment_1''' under the team member's sub-sub-directory## Copy the source files for assignment 1 into this directory, compile it and run it. See [http://zenitOnce it runs successfully, you are ready to add it to the repository server## Move to the head of the repository directory and add the new directory structure along with the source code for the assignment by right clicking on '''.senecac.on.caSVN/wiki/indexAdd''' and checking the folders and files to be added## Commit the directory structure to the repository server by right clicking on '''SVN Commit'''.php/Hints_for_Using_SVN_to_collaborate_on_school_projectsAdd the comment "Created Directory Structure and added assignment 1"##Merging_your_work_back_to_trunk Merging your work back Branch the committed assignment to '''trunk] '''# The repository is now ready for detailseach team member to start working on their own version of the code in their own workspace## Checkout the repository to your own local computer## Branch trunk to your own workspace## Checkout your workspace## Work within your own workspace## Commit your code at the end of each session##* Make sure to add descriptive comments to each commit##* Uncommented commits will not be marked or reviewedIf your team is using Visual Studio as its development platform, mark the '''.sln''', the '''.vcxproj''', the '''.vcxproj.filters''', and the source files as versioned, but not the binaries or executables.

The purpose of this first phase of the project is twofoldBranch submission path:* to define your game in both scope and detail and thereby to give your instructor some idea of your design, so that your instructor can give you some feedback whether what you intend is too simple, too complex, or about right* to show your instructor that you are ready to work with your own branch of your team's repository and ready to start modifying the framework to suit your team's designsvn://zenit.senecac.on.ca/btp300_113_?/branches/SenecaID/assignment1

Your Each team member should decide its own group add their name to individual ratio for grading purposes the header comments of the '''consoleplus.h''' and post '''consolelineedit.cpp''' files as follows:# Edit the source code to include your name# Go to '''trunk'''# Merge your modified source files with '''trunk''' '''...SVN/Merge'''# Go to the agreed ratio on its project page.and change the repo status to "being committed by your name"# Commit to the repository with the comment "name added"# Go back to the project page and change the repo status to "committed by your name"

Your team should arrange a time and date to meet with See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your instructor work back to review your proposal and to identify the different responsibilities of the team members. This meeting should take place during week 6 of the semester.-->trunk] for details