Difference between revisions of "OOP344 - ICANHAZCODE? - 20102"
(Updated with info about mac keyboard code finding) |
(→STATUS) |
||
| Line 18: | Line 18: | ||
Drperit speaking: I was mistaken in what I thought we were supposed to do for phase 1 of the assignment. It turns out that what we need to do is: | Drperit speaking: I was mistaken in what I thought we were supposed to do for phase 1 of the assignment. It turns out that what we need to do is: | ||
| − | Create a skeleton model of iof.c (I | + | Create a skeleton model of iof.c (I have placed this in trunk) |
Have each group member fill in the functions that they were assigned. (I will fill in the unassigned ones, as well). They should do this in their own branches of trunk. Branches can be made in xcode using the copy command in the Repositories window. The project file, when opened, will automatically know that it's a branch and will commit to the correct branch directory. | Have each group member fill in the functions that they were assigned. (I will fill in the unassigned ones, as well). They should do this in their own branches of trunk. Branches can be made in xcode using the copy command in the Repositories window. The project file, when opened, will automatically know that it's a branch and will commit to the correct branch directory. | ||
Revision as of 15:35, 4 June 2010
Y HALO THAR!
HAI CAN HAS STDIO? VISIBLE "HAI WORLD!" KTHXBYE
ANNOUNCEMENTS
None active
STATUS
SVN logins should have been received by all group members
Drperit speaking: I was mistaken in what I thought we were supposed to do for phase 1 of the assignment. It turns out that what we need to do is:
Create a skeleton model of iof.c (I have placed this in trunk)
Have each group member fill in the functions that they were assigned. (I will fill in the unassigned ones, as well). They should do this in their own branches of trunk. Branches can be made in xcode using the copy command in the Repositories window. The project file, when opened, will automatically know that it's a branch and will commit to the correct branch directory.
Once you are done the previous step, you should manually merge your changes back into trunk, assuming that it compiles.
Please test the trunk code on any platforms that you have access to, so that we can e-mail fardad with news of our completion.
I am now sending e-mails to you people, so that you all know what to do.
Adrian, if this is what you were doing when you were copying the code over function by function and I told you just to copy the whole thing over, then sorry.
Also, I found a utility at http://softwares.bajram.com/utilities/#Full_Key_Codes that may be useful for figuring out the mac keyboard codes.
IRC LOGS
WEEK3 - Figured out coding style and divided functions for first assignment
DEVELOPERS
| ID | First Name | Last Name | Team Name | Section | Seneca Id | wiki id | IRC nick | Blog URL |
|---|---|---|---|---|---|---|---|---|
| A | David | Perit | ICANHAZCODE? | A | drperit | dperit | dperit | Code Void |
| B | Volodymyr | Dryzhepolov | ICANHAZCODE? | A | vdryzhepolov | vladimir | Vovko | My Blog |
| C | Adrian | Maurer | ICANHAZCODE? | A | amaurer | Adgezaza | adgezaza | AO Blog |
| D | Jason | Burton | ICANHAZCODE? | A | jaburton1 | jaburton1 | jaburton1 | Invincibly Ignorant |
