Difference between revisions of "OOP344 Team Funktion"

From CDOT Wiki
Jump to: navigation, search
(→‎1st IRC Meeting with Fardad)
(→‎Scheduled Meetings)
 
(165 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
=Team Funktion=
+
[[OOP344]] - [[OOP344 Student List]] - [[OOP344 Teams]] - [[OOP344 Assignment One]] - [[OOP344 Assignment Two]] - [[OOP344 IRC Schedules 20093|OOP344 IRC Schedules]]<br />
 +
 
 +
=SVN=
 +
 
 +
ops344_093a14
 +
 
 +
=Upcoming Schedule=
 +
 
 +
 
 +
*********** '''(OPTIONAL) Team Meeting but highly recommended!!!
 +
 
 +
Tuesday, December 08, 2009 at 17:10
 +
 
 +
In person meeting in room 1133 in the Seneca@York library
 +
Be prepared to demonstrate your assigned class in it's current state
 +
 
 +
Please contact Ljubomir asap to verify if you will be attending this meeting.
 +
 
 +
.'''
 +
 
 
==Team Members==
 
==Team Members==
 
{| border="1" cellpadding="5"
 
{| border="1" cellpadding="5"
  
−
! Last Name !! First Name !! Seneca Username !! Section !! Blog Url !! IRC Nick
+
! Last Name !! First Name !! Seneca Username !! Section !! SVN Repo ID !! Blog Url !! IRC Nick !! Phone Number
 
|-
 
|-
−
| Austerberry ||Eric||erausterberry|| C || [http://oop-era.blogspot.com/ Eric's Blog]|| ericausterberry
+
| Austerberry ||Eric||erausterberry|| C || ops344_093svn143 || [http://oop-era.blogspot.com/ Eric's Blog]|| ericausterberry || -
 
|-
 
|-
−
| Chan || Anton || canton || A || [http://acfunktron.blogspot.com/ AC's Blog] || canton
+
| Chan || Anton || canton || A || ops344_093svn142 ||  [http://acfunktron.blogspot.com/ AC's Blog] || canton || (647) 887-3539
 
|-
 
|-
−
| Cho || Ahreum || acho14 || A || [http://acho14.blogspot.com/ Arum's Blog] || acho14
+
| Cho || Ahreum || acho14 || A || ops344_093svn141 || [http://acho14.blogspot.com/ Arum's Blog] || acho14 || -
 
|-
 
|-
−
| Gorscak || Ljubomir || gljubomir || A || [http://ljubomirgorscak.blogspot.com Ljubomir's Blog] || ljubo
+
| Gorscak || Ljubomir || gljubomir || A || ops344_093svn146 ||  [http://ljubomirgorscak.blogspot.com Ljubomir's Blog] || ljubo || (647) 328-4807
 
|-
 
|-
−
| Li || Verity || vzli || B || [http://starbuck-blog.blogspot.com/ Verity's Blog] || cubicu
+
| Li || Verity || vzli || B || ops344_093svn148 ||  [http://starbuck-blog.blogspot.com/ Verity's Blog] || cubicu || -
 
|-
 
|-
−
| Pezeshki || Neda || npezeshki || C || [http://nedape.blogspot.com/ Neda's Blog] || neda
+
| Pezeshki || Neda || npezeshki || C || ops344_093svn147 ||  [http://nedape.blogspot.com/ Neda's Blog] || neda || -
 
|-
 
|-
−
| Piltz || Jonathan || jmpiltz ||C || [http://jmpiltz.blogspot.com/ Jon's Blog] || Mr_88
+
| Piltz || Jonathan || jmpiltz ||C || ops344_093svn145 ||  [http://jmpiltz.blogspot.com/ Jon's Blog] || Mr_88 || (416) 738-9256
 
|-
 
|-
−
| So || Hyunju || hso3 || A || [http://fromsilver1.blogspot.com/ Hyunju's Blog] || hso3
+
| So || Hyunju || hso3 || A || ops344_093svn144 ||  [http://fromsilver1.blogspot.com/ Hyunju's Blog] || hso3 || -
 
|-
 
|-
 
|}
 
|}
Line 30: Line 49:
 
| Ljubomir Gorscak || gljubomir@learn.senecac.on.ca
 
| Ljubomir Gorscak || gljubomir@learn.senecac.on.ca
 
|-
 
|-
−
| 2nd Person ||-
+
| Jonathan Plitz ||jmpiltz@learn.senecac.on.ca
 
|-
 
|-
 
|}
 
|}
  
−
=First IRC Meeting with Fardad=
+
=First IRC Meeting with Fardad - SVN steps=
−
==Summary==
 
  
 +
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...
  
−
The code you are working on now will be in "trunk".
+
==Summary==
  
−
In trunk, Fardad created a folder called "PRJ".
+
*'''"Check out"''' the repository.
  
−
svn://zenit.senecac.on.ca/ops344_093a14/trunk/PRJ
+
*The code you are working on now will be in '''"trunk"'''.
  
−
In PRJ you will have a directory called "DOS".
+
*In trunk, Fardad created a folder called '''"PRJ"'''.
 +
**svn://zenit.senecac.on.ca/ops344_093a14/trunk/PRJ
  
−
Put source codes inside PRJ.  Everything.
+
*In PRJ you will have a directory called '''"DOS"'''.
  
−
There is one text file with "your_name.txt".
+
*Put source codes inside PRJ. Everything.
  
−
If something is important and you want your team to know about it, you change the date and write it in your_name.txt.
+
*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
 
By the next meeting, we must have the full repository created made
 
build-able with all the classes mentioned in as2 desc.
 
build-able with all the classes mentioned in as2 desc.
  
−
==Here is an (edited) transcription of our meeting with Fardad==
+
==An (edited) transcription of the IRC meeting==
  
−
Check out the repository:
+
'''Check Out''' the repository:
  
−
Create a dir,  and either use svn checkout by right clicking on the directory or type: svn co svn://zenit.senecac.on.ca/ops344_093a14/trunk/PRJ
+
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 soon, 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
+
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?
+
''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"
+
''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?
+
*ljubo: Why did '''"export"''' mess things up so bad?
  
 
*fardad: Well, what happened is that you created a repository inside a repository.
 
*fardad: Well, what happened is that you created a repository inside a repository.
Line 74: Line 95:
 
checkout working copies on your computer from that repository.  The commands you use are mostly:
 
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
+
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
+
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==
 
==Lets go through the steps==
  
−
1st - checkout the code from the repository...
+
'''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)
  
−
you gotta have an organizer the one how makes sure the tasks are
+
'''2nd''' - The organizer must add the following files to the repository.
−
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.
−
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.
 
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)
+
'''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.
 
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
+
'''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.
−
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.
 
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.
+
'''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
+
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
−
stages of the project where you work on the same main
 
  
−
So what I want to see by next meeting:
+
==Fardad's expectations==
 +
What I want to see by the next meeting:
  
−
The full repository created made build-able with all the classes
+
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.
−
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.
 
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...
+
You can look at other teams wikis for ideas and you should give ideas and suggestions to others.
 +
 
 +
=Second IRC Meeting with Fardad=
 +
==Steps==
 +
 
 +
1) Assign classes to developers. Each person is to commit their own classes to SVN.
 +
 
 +
Don't let one person do it all.
 +
 
 +
2) Select a coil lib if not already.
 +
 
 +
3) Each student add/modify/commit his/her assigned classes.  Please call the classes and files IO_Whatever.  Create empty classes (but compilable) for classes with no descriptions or the incomplete ones.
 +
 
 +
4) Main gets created and compiled.
 +
 
 +
5) Project file whatever.vcproj is created, tested, added, and committed buy ONE person.
 +
 
 +
6) Everyone else updates their repository.
 +
 
 +
7) Organizer assigns classes with complete description (in the wiki) to be developed.
 +
 
 +
8) Fardad updates the code and checks it and becomes happy and enjoys his life!!!!
 +
 
 +
==Comments==
 +
'''Mr_88:''' I think we can all agree that step 8 is the best one :)
 +
 
 +
'''Fardad:''' Again I expect blogs from those who didn't have it (short and to the point).  Don't write the story of your life in the blog.  Do the .txt files and update what you have done.
 +
 
 +
'''Fardad:''' What we are doing in OOP344 has never been done anywhere, and the world is watching now, and I am not kidding when I say that.
 +
 
 +
=Other Team IRC Meetings=
 +
 
 +
==Fardad adds io_textedit==
 +
 
 +
I am going to do IO_TextEdit.
 +
 
 +
I will right the steps as I am doing it
 +
 
 +
#I am adding a headerfile and cpp file to my visual studio
 +
#In solution exp. rightclick on headerfiles, add / new item
 +
#Added code/headerfile: "io_textedit.h"
 +
#Now i am righclicking on sourcefiles/newitem code/cpp file
 +
#Added save (gard?) code to the headerifle
 +
#Included general headerifle in io_textedit.h. It will have all necessary definitions and includes for the project
 +
#Adding io_textedit.h and io_textdit.cpp to rep
 +
#Compiled and it was successful, so I will commit now
 +
 
 +
Done, you can now update you working copy and see what I did.  You should do the same for all the other classes.  It should not take you more than 30 minutes to do you part, just pick a class and write it.
 +
 
 +
==Questions==
 +
 
 +
'''klim4:''' What is the general headerfile?
  
 +
'''fardad:''' io_def.h
  
−
==To Do: 10-29-09==
+
'''klim4:''' We do not add our solutions to the repository do we?
 +
 
 +
'''fardad:''' No. Only PRJ.vcproj, which I already did
 +
 
 +
=To Do=
 +
 
 +
==12-06-09==
 +
 
 +
'''Please do this asap!!!'''
 +
 
 +
1) Update your local computer to reflect the current state of our SVN repository.
 +
 
 +
2) Change the project files so that your most recent contributions are included (be sure to communicate with others if you made changes to a class that was not assigned to you).
 +
 
 +
3) Write about what you did in your user.txt file
 +
 
 +
4) Add/Commit the files back to SVN so that other team members can work with your code.
 +
 
 +
5) Blog
 +
 
 +
==11-10-09==
 +
 
 +
Each team member should choose at least one class, and put it beside their name (you may have more than one, including ones that Fardad started or covered in his lectures). Remember, being assigned a class does '''NOT''' mean that you have to write it by yourself! All it means is that you are ultimately responsible for making sure it works properly. Ideally, we will be involved with many classes, and we should understand them all.
 +
 
 +
{| border="1" cellpadding="5"
 +
 
 +
! IRC Nick !! Current Task !! Status
 +
|-
 +
| ericausterberry || io_label || in Progress
 +
|-
 +
| canton || io_edit, Vedit || IO_Edit = 90% complete, Vedit = 90% complete. Minor Tweaks and Testing remains
 +
|-
 +
| acho14 || io_textedit || in Progress
 +
|-
 +
| ljubo ||io_form || io_form can be created, framed, and contain classes that inherit io_field.
 +
|-
 +
| cubicu ||io_field, io_textedit || field done, textedit in progress
 +
|-
 +
| neda ||io_menu, io_form || IO_menu complete, io_form in Progress
 +
|-
 +
| Mr_88 || io_frame || Complete
 +
|-
 +
| hso3 ||io_textedit || in Progress
 +
|-
 +
| fardad ||io_checklist || complete
 +
|-
 +
|}
 +
 
 +
'''Options:'''
 +
*<s>io_field</s>
 +
*<s>io_frame</s>
 +
*<s>io_form</s>
 +
*<s>io_label</s>
 +
*<s>io_edit</s>
 +
*<s>io_vedit</s>
 +
*<s>io_checklist</s>
 +
*<s>io_menu</s>
 +
*<s>io_textedit</s>
 +
 
 +
==11-03-09==
 +
This class assigning was only for the purpose of uploading empty (but compiled) files to SVN. See the current tasks starting November 10th for a more updated list.
 +
 
 +
Note: This menu is no longer relevant to the assignment. Ignore this table and look at the one below.
 +
 
 +
{| border="1" cellpadding="5"
 +
 
 +
! IRC Nick !! Upload Empty to SVN
 +
|-
 +
| ericausterberry || io_checklist
 +
|-
 +
| canton || io_edit
 +
|-
 +
| acho14 || io_label
 +
|-
 +
| ljubo ||io_menu
 +
|-
 +
| cubicu ||io_menubar and io_field
 +
|-
 +
| neda ||io_form
 +
|-
 +
| Mr_88 || main
 +
|-
 +
| hso3 ||io_textedit
 +
|-
 +
|}
 +
 
 +
'''Bonus classes:'''
 +
 
 +
*io_form
 +
*io_frame
 +
*io_field
 +
 
 +
==10-29-09==
 
(by Thursday October 29, 2009 - 12:00)
 
(by Thursday October 29, 2009 - 12:00)
  
Line 130: Line 290:
 
Remember: Fardad asked us to blog "about what we expect to be done and not to be done in the next meeting."
 
Remember: Fardad asked us to blog "about what we expect to be done and not to be done in the next meeting."
  
 +
=Scheduled Meetings=
 +
 +
==01-04-10==
 +
 +
Anton and Ljubo are meeting at Seneca@York library around 12:00.
 +
 +
==12-14-09==
 +
'''Final Week of school for this semester'''
 +
 +
Please indicate all the times that you are available to work on as2, and if you will be at '''school''' or '''online'''.  If two or more people are available at the same time, it may be good to book a private study room.
  
−
==Scheduled Meetings==
+
[https://www.senecac.on.ca/roombooking/index.html Room Bookings]
 +
* Remember to select Seneca@York campus
  
 +
Also, please use the user.txt files '''IN THE TRUNK''' to indicate what you have done, even if your work is posted in another folder.  If something is not updating proper, send the team an email.
 +
 +
This is going to be a real challenge to coordinate and execute because of so many involved.  Communication is the key!
 +
 +
===Team Members Availability===
 +
 +
{| border="1" cellpadding="5"
 +
 +
! IRC Nick !! Monday !! Tuesday !! Wednesday !! Thursday !! Friday
 +
|-
 +
| ericausterberry || busy with exams || After 16:30 at school || All day whereever needed || ditto || ditto
 +
|-
 +
| canton || - || - || - || - || -
 +
|-
 +
| acho14 || - || - || - || - || -
 +
|-
 +
| ljubo || Online - All day || Library 09:00 - 11:00 and 17:00 - 20:00 || Library 10:00 - 15:00 || Library 10:00 - 18:00 || -
 +
|-
 +
| cubicu || - || - || Online || 14:00 - indefinitely || all day
 +
|-
 +
| neda || - || After 16:00 || - || 12:30 || -
 +
|-
 +
| Mr_88 || - || 16:30 onwards || all day || all day || all day
 +
|-
 +
| hso3 || - || - || - || - || -
 +
|-
 +
| fardad || - || - || - || [http://zenit.senecac.on.ca/wiki/index.php/OOP344_IRC_Schedules_20093#Project_Presentation_Meeting IRC Meeting - 14:00] || -
 +
|-
 +
|}
 +
 +
 +
'''ljubo:''' I booked room# 1135 in the library on Tuesday starting at 17:10 until 19:00 (maybe someone can book after 19:00 if we continue later?).  I'm going to look into getting a projector so that it will be easy to look at the same code without squinting at the tiny screen (no promises though).
 +
 +
'''Mr_88:''' If anyone wants to work on the assignment in person, send me an e-mail, else I probably won't show.
 +
 +
'''ljubo:''' I may not be able to work the entire time indicated.  For example, on Monday I plan to study for DBS301 a lot during the day.  I put those times so that if more people want to work at the same times, I will adjust my plans to make myself available.
 +
 +
==12-08-09==
 +
Tuesday, December 08, 2009 at 17:10
 +
 +
'''Optional, but highly recommended!!!'''
 +
 +
*In person meeting in room 1133 in the Seneca@York library
 +
** Be prepared to demonstrate your assigned class in it's current state
 +
 +
Please contact Ljubomir asap to verify if you will be attending this meeting.
 +
 +
==11-28-09==
 +
***OPTIONAL MEETING
 +
 +
Saturday at approx. 12:00 pm (msg ljubo, neda, Anton for details)
 +
* Topics include : walkthrough of assignment
 +
** work on assignment (io_form, Io_label, io_edit)
 +
 +
==11-24-09==
 +
Tuesday, November 24, 2009 at 17:15
 +
 +
*In person meeting in room 1131 in the Seneca@York library
 +
 +
==11-07-09==
 +
Saturday, November 7, 2009 at 12:00 noon
 +
 +
*IRC Meeting with Fardad
 +
 +
==11-05-09==
 +
Thursday, November 5, 2009 at 19:00
 +
 +
*IRC Meeting with Fardad '''CANCELLED'''
 +
 +
==11-04-09==
 +
Wednesday, November 4, 2009 at 17:15
 +
 +
* In person meeting in the library at Seneca@York.  Meeting is in room# 1135.
 +
** Main topic is to Review Assignment 2
 +
 +
==10-29-09==
 +
Thursday, October 29, 2009 at 19:00
 +
 +
* 2nd IRC Meeting with Fardad
 +
 +
==10-27-09==
 
Tuesday, October 27, 2009 at 12:35
 
Tuesday, October 27, 2009 at 12:35
  
 
* In person meeting in the library at Seneca@York.  Meeting is in room# 1135.
 
* In person meeting in the library at Seneca@York.  Meeting is in room# 1135.
 +
** Topics include:
 +
*** Review Assignment 1
 +
*** Understanding SVN
  
 
Tuesday, October 27, 2009 at 17:00
 
Tuesday, October 27, 2009 at 17:00
Line 141: Line 396:
 
* 1st IRC Meeting with Fardad
 
* 1st IRC Meeting with Fardad
  
−
Thursday, October 29, 2009 at 19:00
+
=Resources=
 +
 
 +
Audio Recordings:
 +
 
 +
[http://www.ljubomirgorscak.com/recordings/oop344recordings.html Fardad's OOP344 lectures]
 +
 
 +
Webpages:
 +
 
 +
https://cs.senecac.on.ca/~btp300 <-- the degree version of oop344
 +
 
 +
https://cs.senecac.on.ca/~fardad.soleimanloo/oop344/notes/
 +
 
 +
=Discussion=
 +
'''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.
 +
 
 +
'''Ljubomir:''' np - Please feel free!
  
−
* 2nd IRC Meeting with Fardad
+
'''northWind87:''' excellent, thank you so much!

Latest revision as of 10:07, 4 January 2010

OOP344 - OOP344 Student List - OOP344 Teams - OOP344 Assignment One - OOP344 Assignment Two - OOP344 IRC Schedules

SVN

ops344_093a14

Upcoming Schedule

                      • (OPTIONAL) Team Meeting but highly recommended!!!

Tuesday, December 08, 2009 at 17:10

In person meeting in room 1133 in the Seneca@York library Be prepared to demonstrate your assigned class in it's current state

Please contact Ljubomir asap to verify if you will be attending this meeting.

.

Team Members

Last Name First Name Seneca Username Section SVN Repo ID Blog Url IRC Nick Phone Number
Austerberry Eric erausterberry C ops344_093svn143 Eric's Blog ericausterberry -
Chan Anton canton A ops344_093svn142 AC's Blog canton (647) 887-3539
Cho Ahreum acho14 A ops344_093svn141 Arum's Blog acho14 -
Gorscak Ljubomir gljubomir A ops344_093svn146 Ljubomir's Blog ljubo (647) 328-4807
Li Verity vzli B ops344_093svn148 Verity's Blog cubicu -
Pezeshki Neda npezeshki C ops344_093svn147 Neda's Blog neda -
Piltz Jonathan jmpiltz C ops344_093svn145 Jon's Blog Mr_88 (416) 738-9256
So Hyunju hso3 A ops344_093svn144 Hyunju's Blog hso3 -

Contact Persons

Contact Name Email
Ljubomir Gorscak gljubomir@learn.senecac.on.ca
Jonathan Plitz jmpiltz@learn.senecac.on.ca

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...

Summary

  • "Check out" the repository.
  • The code you are working on now will be in "trunk".
  • 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

Fardad's expectations

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.

Second IRC Meeting with Fardad

Steps

1) Assign classes to developers. Each person is to commit their own classes to SVN.

Don't let one person do it all.

2) Select a coil lib if not already.

3) Each student add/modify/commit his/her assigned classes. Please call the classes and files IO_Whatever. Create empty classes (but compilable) for classes with no descriptions or the incomplete ones.

4) Main gets created and compiled.

5) Project file whatever.vcproj is created, tested, added, and committed buy ONE person.

6) Everyone else updates their repository.

7) Organizer assigns classes with complete description (in the wiki) to be developed.

8) Fardad updates the code and checks it and becomes happy and enjoys his life!!!!

Comments

Mr_88: I think we can all agree that step 8 is the best one :)

Fardad: Again I expect blogs from those who didn't have it (short and to the point). Don't write the story of your life in the blog. Do the .txt files and update what you have done.

Fardad: What we are doing in OOP344 has never been done anywhere, and the world is watching now, and I am not kidding when I say that.

Other Team IRC Meetings

Fardad adds io_textedit

I am going to do IO_TextEdit.

I will right the steps as I am doing it

  1. I am adding a headerfile and cpp file to my visual studio
  2. In solution exp. rightclick on headerfiles, add / new item
  3. Added code/headerfile: "io_textedit.h"
  4. Now i am righclicking on sourcefiles/newitem code/cpp file
  5. Added save (gard?) code to the headerifle
  6. Included general headerifle in io_textedit.h. It will have all necessary definitions and includes for the project
  7. Adding io_textedit.h and io_textdit.cpp to rep
  8. Compiled and it was successful, so I will commit now

Done, you can now update you working copy and see what I did. You should do the same for all the other classes. It should not take you more than 30 minutes to do you part, just pick a class and write it.

Questions

klim4: What is the general headerfile?

fardad: io_def.h

klim4: We do not add our solutions to the repository do we?

fardad: No. Only PRJ.vcproj, which I already did

To Do

12-06-09

Please do this asap!!!

1) Update your local computer to reflect the current state of our SVN repository.

2) Change the project files so that your most recent contributions are included (be sure to communicate with others if you made changes to a class that was not assigned to you).

3) Write about what you did in your user.txt file

4) Add/Commit the files back to SVN so that other team members can work with your code.

5) Blog

11-10-09

Each team member should choose at least one class, and put it beside their name (you may have more than one, including ones that Fardad started or covered in his lectures). Remember, being assigned a class does NOT mean that you have to write it by yourself! All it means is that you are ultimately responsible for making sure it works properly. Ideally, we will be involved with many classes, and we should understand them all.

IRC Nick Current Task Status
ericausterberry io_label in Progress
canton io_edit, Vedit IO_Edit = 90% complete, Vedit = 90% complete. Minor Tweaks and Testing remains
acho14 io_textedit in Progress
ljubo io_form io_form can be created, framed, and contain classes that inherit io_field.
cubicu io_field, io_textedit field done, textedit in progress
neda io_menu, io_form IO_menu complete, io_form in Progress
Mr_88 io_frame Complete
hso3 io_textedit in Progress
fardad io_checklist complete

Options:

  • io_field
  • io_frame
  • io_form
  • io_label
  • io_edit
  • io_vedit
  • io_checklist
  • io_menu
  • io_textedit

11-03-09

This class assigning was only for the purpose of uploading empty (but compiled) files to SVN. See the current tasks starting November 10th for a more updated list.

Note: This menu is no longer relevant to the assignment. Ignore this table and look at the one below.

IRC Nick Upload Empty to SVN
ericausterberry io_checklist
canton io_edit
acho14 io_label
ljubo io_menu
cubicu io_menubar and io_field
neda io_form
Mr_88 main
hso3 io_textedit

Bonus classes:

  • io_form
  • io_frame
  • io_field

10-29-09

(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."

Scheduled Meetings

01-04-10

Anton and Ljubo are meeting at Seneca@York library around 12:00.

12-14-09

Final Week of school for this semester

Please indicate all the times that you are available to work on as2, and if you will be at school or online. If two or more people are available at the same time, it may be good to book a private study room.

Room Bookings

  • Remember to select Seneca@York campus

Also, please use the user.txt files IN THE TRUNK to indicate what you have done, even if your work is posted in another folder. If something is not updating proper, send the team an email.

This is going to be a real challenge to coordinate and execute because of so many involved. Communication is the key!

Team Members Availability

IRC Nick Monday Tuesday Wednesday Thursday Friday
ericausterberry busy with exams After 16:30 at school All day whereever needed ditto ditto
canton - - - - -
acho14 - - - - -
ljubo Online - All day Library 09:00 - 11:00 and 17:00 - 20:00 Library 10:00 - 15:00 Library 10:00 - 18:00 -
cubicu - - Online 14:00 - indefinitely all day
neda - After 16:00 - 12:30 -
Mr_88 - 16:30 onwards all day all day all day
hso3 - - - - -
fardad - - - IRC Meeting - 14:00 -


ljubo: I booked room# 1135 in the library on Tuesday starting at 17:10 until 19:00 (maybe someone can book after 19:00 if we continue later?). I'm going to look into getting a projector so that it will be easy to look at the same code without squinting at the tiny screen (no promises though).

Mr_88: If anyone wants to work on the assignment in person, send me an e-mail, else I probably won't show.

ljubo: I may not be able to work the entire time indicated. For example, on Monday I plan to study for DBS301 a lot during the day. I put those times so that if more people want to work at the same times, I will adjust my plans to make myself available.

12-08-09

Tuesday, December 08, 2009 at 17:10

Optional, but highly recommended!!!

  • In person meeting in room 1133 in the Seneca@York library
    • Be prepared to demonstrate your assigned class in it's current state

Please contact Ljubomir asap to verify if you will be attending this meeting.

11-28-09

      • OPTIONAL MEETING

Saturday at approx. 12:00 pm (msg ljubo, neda, Anton for details)

  • Topics include : walkthrough of assignment
    • work on assignment (io_form, Io_label, io_edit)

11-24-09

Tuesday, November 24, 2009 at 17:15

  • In person meeting in room 1131 in the Seneca@York library

11-07-09

Saturday, November 7, 2009 at 12:00 noon

  • IRC Meeting with Fardad

11-05-09

Thursday, November 5, 2009 at 19:00

  • IRC Meeting with Fardad CANCELLED

11-04-09

Wednesday, November 4, 2009 at 17:15

  • In person meeting in the library at Seneca@York. Meeting is in room# 1135.
    • Main topic is to Review Assignment 2

10-29-09

Thursday, October 29, 2009 at 19:00

  • 2nd IRC Meeting with Fardad

10-27-09

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

Tuesday, October 27, 2009 at 17:00

  • 1st IRC Meeting with Fardad

Resources

Audio Recordings:

Fardad's OOP344 lectures

Webpages:

https://cs.senecac.on.ca/~btp300 <-- the degree version of oop344

https://cs.senecac.on.ca/~fardad.soleimanloo/oop344/notes/

Discussion

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.

Ljubomir: np - Please feel free!

northWind87: excellent, thank you so much!

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OOP344_Team_Funktion&oldid=31845"