Weekly Schedule 20131 - OOP344

From CDOT Wiki
Revision as of 00:29, 17 January 2013 by Daniel Leal Dvorkin (talk | contribs) (blog posts 2)
Jump to: navigation, search


OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources


Week 1 - Jan 6

This Week 1

  • Introduction to Open Source development.
  • Collaboration Tools:
    • Wiki
    • Blog
    • IRC
    • Code Repository
    • Big Blue Button
  • Etherpad
  • Object Orientation Review
  • C Review
    pointers
    pointers and arrays

To Do by Jan 14

  1. Read Pro-git book
    Chapter One and Chapter Two
  2. Create an account on github
  3. Create a blog (anywhere you like)
  4. Join the IRC by registering your nickname on freenode server and joining the #seneca-oop344 channel for 344 related dialog
    Additional channels of interest: #seneca to interact with all Seneca students participating in opensource projects, and #seneca-social for Social (off-topic) dialog.
  5. Select a team of four students and pick a name for you team
  6. Send one email per team to me and send your github and team information
    subject of the email should be 344info20131
    email content
    team name:
    nickname 1:
    name 1:
    surname 1:
    seneca username 1:
    github id 1:
    ------------
    nickname 2:
    name 2:
    surname 2:
    seneca username 2:
    github id 2:
    etc.....
    number of team members:
  7. Create an account on this wiki: send an email to cdot-wiki-admin@senecac.on.ca and ask for an account, an email will be sent back to you with your userid and a temporary password; make sure you have the following included in your email.
    • Email subject: Wiki Account Request
    • The subject you are enrolled in: "OOP344"
    • Your Seneca user id
    • Send this email from your Seneca Account only
  8. Learn how to do basic editing in a wiki
  9. Having all the information above add your name to the student list

Resources 1

Week 2 - Jan 13

This Week 2

  • Real Signature of main()
  • Git Quick review
    clone, pull, push
    branch, add, commit
  • Variable Argument list

To Do 2

  • write 4 command line programs to do
    1. $ add num num<ENTER>
    2. $ sub num num<ENTER>
    3. $ mul num num<ENTER>
    4. $ div num num<ENTER>
  • write a program to show the content of an Operating system environment variable
    $ prnenv path<ENTER>
    The output will be either the "content" of path variable or "not found" if the environment variable does not exist.

blog posts 2

  • http://wp.me/P2Tzoy-7
    There are four programs to be written not one! also, what if the numbers are not valid?
    If using atoi(), do include cstdlib.

resources 2