|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 starting stage 2, please do the following# Read read [[Hints for Using SVN to collaborate on school projects]]and do the following:# Update your team's wiki page with your team's repository path information under '''Repo Path'''# Add assignment 1 to the trunk of your team's repositoryas follows

## Create the branches, tags, and trunk subdirectoriesunder this new directory## Under the branches subdirectory create a sub-subdirectory for each team memberusing their seneca id## Under the sub-subdirectory for one of the team leader's branch members create 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. Once it runs successfully, you are ready to add it to the repository server## Move up to the head of the repository directory and add this the new directory structure along with the source code for the assignment by right clicking on '''...SVN/Add'''and checking the folders and files to be added## Commit the directory structure to the repository server by right clicking on '''SVN Commit'''. Add the comment "Created Directory Structure"## Add and added assignment 1 to the branches sub-directory, compile it, and run it. If the assignment runs successfully add it and commit it to the repository"

## Your The repository is now ready for each team members can now member to start working on their own work  ## Create an Visual Studio Project named '''assignment_1''' in '''trunk'''Your team members should checkout your team's empty repository,add version of the branches, tags, and trunk directoriesand create the initial code [[]]in their own workspace# Create a directory with your seneca id under # Checkout the branch sub-directory of your team's repository. This will be to your home directory for development. For details see own local computer==== Directory Structure ====<big><pre>|-- Team_Repository_Account +--branches | +-- member-id1 <-- this is a team member's home within branches | +-- Task1 | +-- Task2 | +-- member-id2 <-- this is a team member's home within branches | +-- Task1 | +-- Task2 | +-- Task3 | +-- member-id3 <-- this is a team member's home within branches | +-- Task1 +--tags | +-- R0.1 | +-- R0.11 | +-- R0.2 | +-- R0.21 | +-- ... | +-- R0.3 | +-- R0.31 | +-- ... | +-- R1.0 | +-- R1.1 +--## Branch trunk</pre></big> ===== branches =====* '''branches''' is the common directory for all team members' workspaces. * Each team member should create their to your own home directory or '''workspace''' (member-id1, member-id2,...) for their own development tasks within '''branches'''. * Each team member should divide their ## Checkout your workspace into several sub-directories (workspaces) during the development of the project. These workspaces(Task1, Task2, ...) are usually copies of the '''trunk''' to be worked on.*: ''These sub-directories(Task1, Task2,...) are called branches of trunk. When the word '''branch''' is used as a verb, it means copying the whole '''trunk''' into a sub-directory, either in '''branches''' or '''tags'''.## Work within your own workspace ===== tags =====* '''tags''' is ## Commit your code at the directory that holds '''copies''' of successful stages end of '''trunk''' throughout development. (''Also called as '''Milestones''''')each session##* '''tags''' are never modified or edited. ''You may branch a directory of tag into branches under a workspace and then modify the branch and apply the changes back Make sure to trunk, but you should never change the contents of a tag''* The action of '''branch'''ing the trunk into '''tags''' is often referred add descriptive comments to as a '''release'''.each commit##* We use the '''tags''' directory to submit the work for marking. ''Your instructor Uncommented commits will specify the requirements of a release.not be marked or reviewed** A release If your team is usually tagged by a version number like: R0.1using Visual Studio as its development platform, Prj0.2, As1_1.0 ** When a release is due, your instructor will always mark the latest version of that release. **: ''If R0.3 is due, and R0.3, R0.31, R0'.32 are present in '''tagssln''', then your instructor will mark R0.32 ===== trunk =====* '''trunk''' is the directory that holds the project in its current stage, '''complied and run-able'''* '''trunk''' should never hold non-compiled code. Usually trunk is an exact copy (or better than) the latest version in vcxproj'''tags'''.* Since only one project is within the repository, trunk has no project level sub-directory and is the root of the project.  <!--# 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.senecacvcxproj.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]filters''  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 the team members' Framework workspaces back to trunk so that , and the caption of source files as versioned, but not the dialog box shows all of the names of the team members. See [http://zenit.senecacbinaries or executables.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk] for details

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