1
edit
Changes
→Second meeting notes
8- if you are talking about a program you wrote and want to show it to your friends use the http://pastebin.ca website to copy the text and post it, then copy the url and put pass the usl also, if you have a very long URL and want to give it to others, do this: use http://tinyurl.com/to copy your url and make is small.... when you click on the short url, tinyurl.com will redirct you to the long one :)
== Second meeting ==
At this meeting, Fardad distinguished function of three directories(branch/tag/trunk) in SVN for us. It 's also the rules for our OOP project in the future.(Some sentences are quoted from Fardad)
'''Branches:'''
''Purpose'' : It may be team member's another code backup place. Branches is the directory that team members can commit to even if their code does not compile. In the branches, the subdirecotires that are copies of trunk to work on a part of a project are called workspaces.
''How '': Each team member should create their own sub-directory in it and name it with same name of their learn ID. Meanwhile, they may created several sub-directory in their own directory for the item which they are working on. Each team member update the trunk, apply her/his successful changes to the trunk, compile, update again , compile and then commit. But they should only commit to trunk, when their code are tested and proved to work in the branches directory of them.
''Example '': if "fsoleima" working on function/class "putstr", "backspace" and "delete", then the branches should look like:
branches-|
|-fsoleima
| |-putstr
| |-backspace
| |-delete
|
|-other one
.
.
.
the last three directories and copies of trunk in which team member work on her/his part of the project. The team members may commit their own work at anytime, and it won't ruin others work.
'''Tags'''
''Purpose'' : It is the direcotry that keeps copies of successful points of the project.
''How'' : All these snapshots and copies are done using the branch command. Right click on trunk and then select branch and right the destination of copy, if team member branch into branches dir, then it is creating a workspace. If team member branch into tags dir then it means their trunk is at a sucess stage and they are creating a milestone.
''Example'': For our text editor project, the first time the frame of the text editor is done, although the test editor in no way is complete of functional, but one step of the way is completed. At this moment, a snapshot of trunk is taken, and it is copied to the tags directory as a milestone of the project. Usually it is called with sequential names like: m01,m02... or TextEdit01-frame , TextEdit02_SaveAsDialog
'''Trunks'''
''Purpose'' : Trunk is the current state of project and it should and is ALWAYS in a compiled state. It is root of project, and it should have NOTHING other that the main unique project in hand.
''How'': For our team, there are supposed 8 text files (9 including Fardad) with team member names on them, in case they have somthing to say.
