Difference between revisions of "OOP344 Team Funktion"
(→Lets go through the steps)
(→OOP344 Team Temporary northWind87: Added a discussion section and added a comment)
|Line 145:||Line 145:|
* 2nd IRC Meeting with Fardad
* 2nd IRC Meeting with Fardad
Revision as of 16:43, 29 October 2009
|Last Name||First Name||Seneca Username||Section||Blog Url||IRC Nick|
First IRC Meeting with Fardad - SVN steps
Our first meeting with Fardad was on Tuesday October 27, 2009 at 17:00. Our team experienced a few problems with SVN. A summary, and an edited transcription follows...
- "Check out" the repository.
- The code you are working on now will be in "trunk".
- In trunk, Fardad created a folder called "PRJ".
- In PRJ you will have a directory called "DOS".
- Put source codes inside PRJ. Everything.
- There is one text file with "your_name.txt".
- If something is important and you want your team to know about it, you change the date and write it in your_name.txt.
By the next meeting, we must have the full repository created made build-able with all the classes mentioned in as2 desc.
An (edited) transcription of the IRC meeting
Check Out the repository:
Create a dir, and either use svn check out by right clicking on the directory or type: svn co svn://zenit.senecac.on.ca/ops344_093a14/trunk/PRJ
You must cd to the directory you created first. It will ask for the user id and password then you start working with the copy you just checked out. Add files, modify already existing files and so on, when you are done with your changes, you right-click on the dir and click on "svn commit" or type svn commit. This will apply the changed you make to the repository.
Now what if someone already made changes to repository?
Easy: You just right-click on svn update or type svn update and this will apply the changes to YOUR working local copy is you want to see what is on the repository it is "svn list".
- ljubo: Why did "export" mess things up so bad?
- fardad: Well, what happened is that you created a repository inside a repository.
Lets understand this that there is a repository on zenit and you checkout working copies on your computer from that repository. The commands you use are mostly:
Check out (only once) and then update, commit, list when you commit your code to the repository.
You can always checkout your code to another computer and work on it and then commit, then when you go back to your computer at home, you simply do an update and all the changes you made at school, will be applied your code at home.
Lets go through the steps
1st - checkout the code from the repository.
You gotta have an organizer the one who makes sure the tasks are assigned properly, (I recommend you have the same as the contact person)
2nd - The organizer must add the following files to the repository.
The io_def.h with ciol.h included for cpp in there (with extern and everything) and a prjmain.cpp file with a main and 8 "sub-main" functions for each developer. You can call those functions like: int neda_main() or canton_main() and so on. The real main function (main) should use have only one function call in it to one of those sub-main functions.
Each of you can have his/her own main to test what they are developing and update and commit will not ruin other developer's main. The only thing you need to do after an update, is to change on function call in main.
3rd - choose the best ciol written and add it to the repository or m (all these are being added to the PRJ directory)
When I say add the file to repository, all you do is to add the file to your working copy and then issue svn add filename (or right-click on it and then svn add) and the svn commit. Remember when you add a file, it will be marked to be added on next commit.
4th - Each developer checks out the code and then adds a "your_name".txt to the Docs dir in PRJ. This file is used as a log to register all you do currently, most recent task is on top then the organizer will assign classes to each developer from the definition of assign 2.
All you do first is to create a header file and cpp file with the same name as the class name, and then build the working copy and make sure it compiles. When you reached to a build-able stage, you commit the code so other developers can get the class in next update.
NEVER COMMIT A CODE THAT DOES NOT COMPILE. Your PRJ must always be build-able.
You have your own main testing your own class, it is at the final stages of the project where you work on the same main
What I want to see by the next meeting:
The full repository created made build-able with all the classes mentioned in as2 desc. Just create the header-file and cpp file. I need to know who created which class by looking at the docs directory and your logs.
I expect you all to blog about this meeting.
You can look at other teams wikis for ideas and you should give ideas and suggestions to others.
(by Thursday October 29, 2009 - 12:00)
1) Follow the steps to "check out" on SVN
2) Add a log in your_name.txt file to show we were there
3) Upload assignment 1.
4) Have the full repository created made build-able with all the classes mentioned in as2 desc.
Remember: Fardad asked us to blog "about what we expect to be done and not to be done in the next meeting."
Tuesday, October 27, 2009 at 12:35
- In person meeting in the library at Seneca@York. Meeting is in room# 1135.
- Topics include:
- Review Assignment 1
- Understanding SVN
- Topics include:
Tuesday, October 27, 2009 at 17:00
- 1st IRC Meeting with Fardad
Thursday, October 29, 2009 at 19:00
- 2nd IRC Meeting with Fardad
northWind87: Cool website, I really like the design and contents. I hope that you don't mind us modeling out some of our site's elements after yours? Please feel free to let me know if that bothers you guys.