Changes

Jump to: navigation, search

Weekly Schedule 20103 - OOP344C

3,258 bytes added, 08:06, 20 December 2010
To Do
*[http://zenit.senecac.on.ca/wiki/index.php/OOP344_Student_Resources#Create_an_IRC_account_and_login_.28in_Windows.29Createan IRC account and login (in Windows)]
* [http://zenit.senecac.on.ca/wiki/index.php/RabbitVCS RabbitVCS - Linux alternative to TortoiseSVN]
<!--
== Week 2 - Sep 12 ==
* #define (macros)
* Multi-platform Coding
* Conditional Compilation
* Review of types in C
* svn more detailed
* Starting Basic IO library for the project
=== To Do ===
* If not done already, complete week 1 To Do '''NOW'''.
* Finalize and confirm your teams of 3 (or 4 with Fardad's permission): [[Initial Team Assignments 20103 - OOP344C]] '''due Wed Sep 15 12:00 noon'''.
* Finalize your teams (groups of 4 or five students)* Apply for svn account by sending [mailto:fardad.soleimanloo@senecac.on.ca?subject=oop344_svn- fardad] an email holding the list of your team members in comma separated format (csv) as follows: (1 email per team)== Resources ===
<big><pre>
team name
A,last name1,first name1,seneca id1
B,last name2,first name2,seneca id2
....
</pre></big>
 
=== Resources ===
* [[oop344 20102 - iof functions|Basic Input/Output Functions]]
* [http://en.wikipedia.org/wiki/C_preprocessor Preprocessor Directives]
== Week 3 - Sep 19 ==
=== This Week ===
* IRC in action ([[Sep 21, 2010 class lecture notes for OOP344|class lectures and notes]])
* Casting
* Pointers, Arithmetic
* Arrays, (Multi-dimensional)
* [[oop344 20102 - iof functions|iof]] (continued)
* lazy evaluation
* developing and finalizing basic io library
* Committing your work to svn
* [[Sept 24 2010 class lecture notes for OOP344 | Notes on Pointers, Arrays and Lazy Eval]]
=== To Do ===
* Starting next week, we will try to have one quiz per week.* Create svn directories for your '''development root''' under branches in your project repository (your team svn account) '''due Thu Sep 23 12:00 noon'''* Create test directories under your '''development root''' '''due Thu Sep 23 12:00 noon''': note: ''use your seneca email id as root of your development branch''<big><pre>|-- Team svn account +--branches | +-- member id one <-- this is your "development root" | +-- testdir | +-- member id two | +-- testdir | +-- member id three | +-- testdir +--tags +--trunk</pre></big>* Add C text files to your repo's testdir and exercise Checkout, update, commit, etc... on it. '''due Thu Sep 23 12:00 noon'''
* work with svn and familiarize yourself with it
* Blog,
* Book your first IRC meeting with your prof.
* Get ready for the first quiz on what ever we work on till now
=== Resources ===
 
* [[oop344 20102 May 27 - Online IRC course| May 27 course]]
== Week 4 - Sep 26 ==
* void pointers
* intro to pointer to functions
* [[Oop344_20102_-_iof_functions | Coding iof functions]]developing io library continued
=== To Do ===
* write void MemCpy# Add a blank solution to trunk with the following files:## iol.c(blank file) ## iol.h(void* des, void* src, unsigned int sizeblank header file with safeguard coded only);** this ## ioltest.c a file that includes '''iol.h''' and has conditional compilation set for each developers main() function copies for testing:##: see below for example.# Each team member should branch the contents of src trunk into deshis/her workspace in branches#: Each team member must implement one platform and test it to make sure all the functions work properly# Merge back the workspace to trunk to apply the changes you made. #: Merge, compile trunk, make sure everything works, byte by byte then commit the trunk and branch it to next tag dir sequence.#: First one completing the platform should call the tag prj0.01, next one should call the tag 0.02 and so on....#: Last one completing the assigned platform should call the tag 0.1. ( will mark this tag the latest release after 0.1)# '''Prj0.1 due on Wed 29 noon; '''#: Submit in tags prj0.1 branch (dir) of your team repository#: Simple 'size''iolib''' bytesfunctions are due with your own test program to prove that functions work properly#: One platform must be committed per (and by) team member. (i.e. if you have four team members, you have four platforms to develop)#: Note that in MAC for function keys you should use combination of one of the ctrl, alt or apply keys with the function keys to get a unique key code.#: Minimum number of platforms is 2. which means if you are doing the project alone, you must have at least two platforms.<big> /* ioltest.c example #include "iol.h" #define senecaid1 1 #define senecaid2 2 #define .... #define PROGRAMMER senecaid1 #if PROGRAMMER == senecaid1 int main(){ /* test written by senecaid1 */ return 0; } #elif PROGRAMMER == senecaid2 int main(){ /* test written by senecaid2 */ return 0; } #elif ...... #else int main(){ /* common main for all */ return 0; } #endif</big>
=== Resources ===
* [svn://zenit.senecac.[Hints for Using SVN to collaborate on.ca/oop344/trunk/05-Jun02 iof notesschool projects]]
== Week 5 - Oct 03 ==
* sizeof
* bitwise operators
* [[Oop344_20102_Iolib functions 20103 -_iof_functions OOP344 | Coding iof iolib functions(Q&A)]] continued
=== To Do ===
=== Resources ===
== Week 6 - June 13 Oct 10 ==
=== This Week ===
* Quiz
* bitwise operators (continued)
* bit-fields
* Real Syntax of main()
* Variable Arguments
* Starting C++ and Main Project(Encapsulating '''iolib''')
=== To Do ===
* This weekend all wiki pages and contributions will be marked.
*: make sure all the following are up-to-date
*:# Your information in student list
*:# Your personal page on wiki
*:# Your project development page
*:# Your blog
* Study for Quiz This week & next week
* Next Week Midterm Test* Fill [svnhttps://zenit.senecac.on.ca/svn/oop344/trunk/TeamSelfMarking.ods The Team Self Evaluation From] on a computer , print and hand it inwhen doing the midterm test.* write void printBits(unsigned int) shortest way possible. 
=== Resources ===
 == Week 7 - Oct 10 17 ==
=== This Week ===
=== To Do ===
* Start the main project by dividing tasks between team membersPrj0.2 is due Sunday Oct 17 at 23:59 (in tags, prj0.2 branch)*: All '''iolib''' functions are due 
=== Resources ===
== Week 8 - Oct 24 (Study Week) ==
 
=== This Week ===
* [http://fsoss.senecac.on.ca/ FSOSS]
=== To Do === === Resources === == Week 8 9 - Oct 17 (Study Week) 31==
=== This Week ===
* OOP344 classes are in place Midterm test on Tuesday and Wednesday (12:00 to 14:00, Room S2174 and if majority of the class stays, we can stay more)* Test 1 will be on Wednesday* Main Project Review* Default Parameters* Member Initialization
* Namespaces
* Intro to Linked Lists ??list* File Streams === To Do === === Resources ===* [svnhttp://zenittinyurl.senecac.on.ca/oop344/trunkcom/13-Jun29 Review Session Notes344ProjTalk November 5th IRC Meeting Transcript]
== Week 10 - Nov 07==
 
=== This Week ===
* File Streams
* Binary Files
=== To Do ===
 
=== Resources ===
 
== Week 11 - Nov 14==
* Inline Functions
* Templates
** Functions
** Classes
=== This Week ===
 
=== To Do ===
 
=== Resources ===
 
== Week 12 - Nov 21==
* References
* Inheritance
** Multiple
** Virtual
** Abstract classes (reviewed)
 
=== This Week ===
 
=== To Do ===
<!--* Nov 28, 23:59, Prj 0.6 is due
*: The full object oriented frame work of the application -->
 
=== Resources ===
 
== Week 13 - Nov 28==
=== This Week ===
* Exception Handling
* Casting Reviewed
* Template Library
* Test 2
 
=== To Do ===
 
=== Resources ===
 
== Week 14 - Dec 5==
 
=== This Week ===
* Review
* Exam preparation
=== To Do ===
* Start the main project by dividing tasks between team membersDec 12, 23:59, Prj 0.6 due.* Create Mock-up classes and methods and commit it to the repository: Final release of application is due.
=== Resources ===
-->

Navigation menu