1. What was planned?
*Finish implementing components for Bunny Generals Prototype
*Implement a way to script player actions for tutorial purposes
2. What was done?
*Fix some bugs with Bunny Generals Prototype, HUD, Selection Boxes, Dynamic Swapping, Error Checking
*Reorganized the code to make it easier to work with
*Added some boxes similar to Wu's castle to the HUD for dialogue
3. Problems encountered?
*Scripting the sort sequence so a player can watch it is very tricky.
*End of semester means lots of work on all fronts, only 3 projects simultaneously
4. What did you learn this week?
*I love creators club forums the ultimate resource. You have a problem, someone else has probably already cried about it.
*uber OOP code is not too bad, just annoying
5. What's planned for next week?
*Have a better demo ready for Dr. Barnes, I guess for Tuesday or Wednesday
6. Hours worked.
*About 10
Thursday, April 23, 2009
Wednesday, April 22, 2009
Evie's Weekly report
1. What was planned?
finished fixing problems with for loops
codebase clean up
visually enhanced dance tool
finish implementing xml schema
add survey to the dance tool
get timeline working
get durations implemented
2. What was done?
finished fixing problems with for loops
codebase clean up
visually enhanced dance tool
3. Problems encountered?
Class assignments flared up again...
4. What did you learn this week?
a clean codebase is a happy/ more understandable codebase
5. What's planned for next week?
make some more miracles happen via another code clean up
6. Hours worked.
Alot... lets see... i was here till 3am every day last week. i think that was an extra 30 hours than usual. prolly 70% of that was dance tool time.
finished fixing problems with for loops
codebase clean up
visually enhanced dance tool
finish implementing xml schema
add survey to the dance tool
get timeline working
get durations implemented
2. What was done?
finished fixing problems with for loops
codebase clean up
visually enhanced dance tool
3. Problems encountered?
Class assignments flared up again...
4. What did you learn this week?
a clean codebase is a happy/ more understandable codebase
5. What's planned for next week?
make some more miracles happen via another code clean up
6. Hours worked.
Alot... lets see... i was here till 3am every day last week. i think that was an extra 30 hours than usual. prolly 70% of that was dance tool time.
Yoo-Shin's Weekly Report 4/15 - 4/21
1. What was planned?
I need to make the timeline icon.
2. What was done?
I made an icon with Su-Hyung but I cannot set on timeline box.
3. Problems encountered?
I cannot set an icon where I need and I could not get a plenty time for project because I had many homework and test in my class at last week.
4. What's planned for next week?
I need to finish making timeline icon.
5. Hours worked
5 hours.
Tuesday, April 21, 2009
Acey's Weekly Report 4/15 - 4/21
1. What was planned?
Using the game itself at outreach rather than the old version with paper puzzles.
Get the high score saving working.
Hopefully fixing the lag problem through the use of goal puzzle images overlayed on top of an empty grid.
2. What was done?
Got high score saving working
Implemented unlocking system
Fixed the rounding errors on position
Added a way to get color by clicking on bead
Created the code to reduce lag
Fixed logging bug
3. Problems encountered?
Had a bit of trouble designing the save system file structure but after a few tries I came up with a system that works well.
Due to time constraints at outreach the CSDT portion had to be cut from the schedule this week.
4. What did you learn this week?
All about the problems of blind casting. The rounding error was due to casting doubles to ints before rounding them. This made it cut off any fraction even ones over 1/2. By replacing this code with some rounding the grid now correctly shows the positon of the beads.
5. What's planned for next week?
Take pictures of all the puzzles and fit them into the game. Use these to reduce the lag from huge numbers of beads being on screen at once.
Outreach with the game.
6. Hours worked 18
Using the game itself at outreach rather than the old version with paper puzzles.
Get the high score saving working.
Hopefully fixing the lag problem through the use of goal puzzle images overlayed on top of an empty grid.
2. What was done?
Got high score saving working
Implemented unlocking system
Fixed the rounding errors on position
Added a way to get color by clicking on bead
Created the code to reduce lag
Fixed logging bug
3. Problems encountered?
Had a bit of trouble designing the save system file structure but after a few tries I came up with a system that works well.
Due to time constraints at outreach the CSDT portion had to be cut from the schedule this week.
4. What did you learn this week?
All about the problems of blind casting. The rounding error was due to casting doubles to ints before rounding them. This made it cut off any fraction even ones over 1/2. By replacing this code with some rounding the grid now correctly shows the positon of the beads.
5. What's planned for next week?
Take pictures of all the puzzles and fit them into the game. Use these to reduce the lag from huge numbers of beads being on screen at once.
Outreach with the game.
6. Hours worked 18
Saturday, April 18, 2009
Antoine Weekly Report 4-15-09
1. What was planned?
*Implement the suggestions received from Dr. Barnes and everyone at the gamelab meeting.
*Link up with Katie at some point a create a preliminary GDD, and sitdown and get her up to speed on the code so she can work on it easily, (I probably should clean up the code).
2. What was done?
*Added most of suggestions to the code, still need to find better art that scales up well.
3. Problems encountered?
*Dr. Barnes and myself have conflicting schedules so having time to meet up is proving difficult.
*A GDD for Bunny Generals may have to wait for now, the end up the semester is bringing lots of work.
4. What did you learn this week?
*Using game library's and registering services in XNA( Ketih, and creators.xna.com)
5. What's planned for next week?
*Completely Finish This Bunny General sample(all positive feedback) and implement a logging system for when studies are done.
6. Hours worked.
*About 8 hours.
*Implement the suggestions received from Dr. Barnes and everyone at the gamelab meeting.
*Link up with Katie at some point a create a preliminary GDD, and sitdown and get her up to speed on the code so she can work on it easily, (I probably should clean up the code).
2. What was done?
*Added most of suggestions to the code, still need to find better art that scales up well.
3. Problems encountered?
*Dr. Barnes and myself have conflicting schedules so having time to meet up is proving difficult.
*A GDD for Bunny Generals may have to wait for now, the end up the semester is bringing lots of work.
4. What did you learn this week?
*Using game library's and registering services in XNA( Ketih, and creators.xna.com)
5. What's planned for next week?
*Completely Finish This Bunny General sample(all positive feedback) and implement a logging system for when studies are done.
6. Hours worked.
*About 8 hours.
Tuesday, April 14, 2009
Acey's Weekly Report 4/8 - 4/14
1. What was planned?
Put finishing touches on Custom GUI elements then work on the save system.
Find Easter Eggs.
2. What was done?
Found Easter Eggs
Finished the custom GUIs
Implemented High Score Loading
Game now logs all the players actions while playing the game
3. Problems encountered?
Still dealing with lag issues on more complex puzzles, but I think I have found a nice fix for it.
4. What did you learn this week?
Learned a bit about logging data.
5. What's planned for next week?
Using the game itself at outreach rather than the old version with paper puzzles.
Get the high score saving working.
Hopefully fixing the lag problem through the use of goal puzzle images overlayed on top of an empty grid.
6. Hours worked
18
Put finishing touches on Custom GUI elements then work on the save system.
Find Easter Eggs.
2. What was done?
Found Easter Eggs
Finished the custom GUIs
Implemented High Score Loading
Game now logs all the players actions while playing the game
3. Problems encountered?
Still dealing with lag issues on more complex puzzles, but I think I have found a nice fix for it.
4. What did you learn this week?
Learned a bit about logging data.
5. What's planned for next week?
Using the game itself at outreach rather than the old version with paper puzzles.
Get the high score saving working.
Hopefully fixing the lag problem through the use of goal puzzle images overlayed on top of an empty grid.
6. Hours worked
18
Thursday, April 9, 2009
Antoine Campbell Weekly Report 4-8-09
1. What was planned?
*Demo with Dr. Barnes for feedback
*Work with Katie on Bunny Generals
*Modify Bunny Generals from feedback
2. What was done?
*Modified Bunny Generals from student feedback, to make more intuitive
*Demoed with Dr. Barnes, got lots of feedback
*Katie showed the game to gamelab students and Dr. Youngblood, even more feedback.
3. Problems encountered?
*Katie apparently has a busy schedule and I work all the time and it'll be hard to work together in the same room at the same time. But their is always email and what not.
4. What did you learn this week?
*There is a lot of potential in this concept and the Prototype seemed well received and everyone was very helpful with their feedback.
*Iterative Game Development is preferred when developing a game like this, previous games were more for myself than anything and a development process not based on analysis and testing would not be ideal since this prototype is not for me, but for students.
Be sure to cite any resources you used (e.g. online tutorials, etc).
5. What's planned for next week?
*Implement the suggestions received from Dr. Barnes and everyone at the gamelab meeting.
*Link up with Katie at some point a create a preliminary GDD, and sitdown and get her up to speed on the code so she can work on it easily, (I probably should clean up the code).
6. Hours worked.
About 16 hours.
*Demo with Dr. Barnes for feedback
*Work with Katie on Bunny Generals
*Modify Bunny Generals from feedback
2. What was done?
*Modified Bunny Generals from student feedback, to make more intuitive
*Demoed with Dr. Barnes, got lots of feedback
*Katie showed the game to gamelab students and Dr. Youngblood, even more feedback.
3. Problems encountered?
*Katie apparently has a busy schedule and I work all the time and it'll be hard to work together in the same room at the same time. But their is always email and what not.
4. What did you learn this week?
*There is a lot of potential in this concept and the Prototype seemed well received and everyone was very helpful with their feedback.
*Iterative Game Development is preferred when developing a game like this, previous games were more for myself than anything and a development process not based on analysis and testing would not be ideal since this prototype is not for me, but for students.
Be sure to cite any resources you used (e.g. online tutorials, etc).
5. What's planned for next week?
*Implement the suggestions received from Dr. Barnes and everyone at the gamelab meeting.
*Link up with Katie at some point a create a preliminary GDD, and sitdown and get her up to speed on the code so she can work on it easily, (I probably should clean up the code).
6. Hours worked.
About 16 hours.
Wednesday, April 8, 2009
Katie's Weekly Report 4/8/2009
1. What was planned?
-Sixth session with Citizen Schools, student game development will continue
-Absolutely need to have a study design or proposal for Creativity and Cognition
-Tapia 2009 (aka Samantha & Katie's Oregon Trail Adventure) in 1 week, need to finalize paper and plan our session with STARS
-Have a playable Bunny Generals prototype in 2 weeks
2. What was done?
-6th and 7th Citizen Schools sessions
-Tapia Poster and Tapia Presentation
-Playable Bunny Generals Prototype, and Bunny Generals Presentation
3. Problems encountered?
-Citizen Schools outreach is going much slower than expected, we'll have to intervene heavily to get student games completed
-Flying is terrible, terrible, terrible
-Not having a lab computer is mildly irritating. I wish Megaman wasn't dead.
-More focus needs to be put on Bunny Generals in order to have a solid basis completed by Summer
4. What did you learn this week? (esp. computer science, or anything surprising or
interesting) Be sure to cite any resources you used (e.g. online tutorials, etc).
-Tons of great stuff at Tapia about other schools/research/presentations/etc.
5. What's planned for next week?
-Creativity & Cognition?
-Focus on Bunny Generals -> Integrate code and pass counting in order to clarify the link between the game and the CS concepts being taught
-Citizen Schools intervention, we'll be assisting in the completion of student games this week
-Revisit EleMental -> Do a comparison of 2D v. 3D, design a study to track long term learning gains, improve upon the compiler and use of student code
6. Hours worked.
(Since 3/25, including Tapia) 60+
-Sixth session with Citizen Schools, student game development will continue
-Absolutely need to have a study design or proposal for Creativity and Cognition
-Tapia 2009 (aka Samantha & Katie's Oregon Trail Adventure) in 1 week, need to finalize paper and plan our session with STARS
-Have a playable Bunny Generals prototype in 2 weeks
2. What was done?
-6th and 7th Citizen Schools sessions
-Tapia Poster and Tapia Presentation
-Playable Bunny Generals Prototype, and Bunny Generals Presentation
3. Problems encountered?
-Citizen Schools outreach is going much slower than expected, we'll have to intervene heavily to get student games completed
-Flying is terrible, terrible, terrible
-Not having a lab computer is mildly irritating. I wish Megaman wasn't dead.
-More focus needs to be put on Bunny Generals in order to have a solid basis completed by Summer
4. What did you learn this week? (esp. computer science, or anything surprising or
interesting) Be sure to cite any resources you used (e.g. online tutorials, etc).
-Tons of great stuff at Tapia about other schools/research/presentations/etc.
5. What's planned for next week?
-Creativity & Cognition?
-Focus on Bunny Generals -> Integrate code and pass counting in order to clarify the link between the game and the CS concepts being taught
-Citizen Schools intervention, we'll be assisting in the completion of student games this week
-Revisit EleMental -> Do a comparison of 2D v. 3D, design a study to track long term learning gains, improve upon the compiler and use of student code
6. Hours worked.
(Since 3/25, including Tapia) 60+
Evie's Weekly Report 4-8-09
1. What was planned?
Get Max dancing. Get the bug with loops fixed. Finish IRB. Get evaluation stuff built into tool. Dance Tool paper... get some of that fleshed out.
2. What was done?
Max dances. One bug in loops fixed but in process found a different bug (time stamping problem) should be able to fix that in an hour. IRB draft complete but still need to do informed consent and supplement documents. XML schema completed. Did 8 reviews for the GHC. Assisted in getting delete functionality into dance notes and currently debugging some xml problems.
3. Problems encountered?
Just the simple problem of not having enough hours in the day.
4. What was learned?
XML schemas are good for more than just looking pretty. Now the key is finding a tool for the mac that turns my schema into magic.
5. What's planned for next week?
harrass teammates some more on completing their IRB tutorial. Wrap up eval stuff by Thursday. Create pre and post test and user survey.
6. Hours worked?
32 hours
Tuesday, April 7, 2009
Acey's Weekly Report 4/1 - 4/7
1. What was planned?
Get the remaining puzzles in.
Begin Work on Saving System
2. What was done?
With the help of Hugh I got all the puzzles in and working. However after getting feedback from various people I worked on improving the user interface and getting a puzzle selection menu working rather than working on the save system.
Added Puzzle Selection Menu (Displays High Score and Medal)
Added a new custom color selection menu
Did a small amount of optimization for menu actions
3. Problems encountered?
Only problem was realizing it takes a lot longer than I realized to create GUIs. All the GUIS before the selection menu had been just minor edits to existing menus or menus with less than 10 buttons. This one required a lot of design and time to implement. I thought this would take just a bit of my time this week but it ended up taking a good chunk of it.
4. What did you learn this week?
Learned a lot about making GUIs from scratch. Hurray GUIs!
5. What's planned for next week?
Put finishing touches on Custom GUI elements then work on the save system.
Find Easter Eggs.
6. Hours worked
18.5
Get the remaining puzzles in.
Begin Work on Saving System
2. What was done?
With the help of Hugh I got all the puzzles in and working. However after getting feedback from various people I worked on improving the user interface and getting a puzzle selection menu working rather than working on the save system.
Added Puzzle Selection Menu (Displays High Score and Medal)
Added a new custom color selection menu
Did a small amount of optimization for menu actions
3. Problems encountered?
Only problem was realizing it takes a lot longer than I realized to create GUIs. All the GUIS before the selection menu had been just minor edits to existing menus or menus with less than 10 buttons. This one required a lot of design and time to implement. I thought this would take just a bit of my time this week but it ended up taking a good chunk of it.
4. What did you learn this week?
Learned a lot about making GUIs from scratch. Hurray GUIs!
5. What's planned for next week?
Put finishing touches on Custom GUI elements then work on the save system.
Find Easter Eggs.
6. Hours worked
18.5
Wednesday, April 1, 2009
Acey Weekly Report 3/25 - 3/31
1. What was planned?
Get at elast one puzzle in and provide feedback to player
2. What was done?
I got in half te puzzles and provide feedback to the user.
I also got some feedback from my fellow G2Lers on additional feedback options
3. Problems encountered?
Found a few more bugs and am starting to see some slow down in the run time. The bead size ne shouldnt be too hard to fix but I might have tostart optimizing the original code to speed it up soon.
4. What did you learn this week?
Storig moves is better than storing beads. So much smaller.
5. What's planned for next week?
Get the remaining puzzles in that can be done and begin work on the saving system.
6. Hours worked
18
Get at elast one puzzle in and provide feedback to player
2. What was done?
I got in half te puzzles and provide feedback to the user.
I also got some feedback from my fellow G2Lers on additional feedback options
3. Problems encountered?
Found a few more bugs and am starting to see some slow down in the run time. The bead size ne shouldnt be too hard to fix but I might have tostart optimizing the original code to speed it up soon.
4. What did you learn this week?
Storig moves is better than storing beads. So much smaller.
5. What's planned for next week?
Get the remaining puzzles in that can be done and begin work on the saving system.
6. Hours worked
18
Antoine Campbell Weekly Report 3-30-09
1. What was planned?
*Add some stuff to Bunny Generals from feedback
*Get some feedback from Dr. Barnes
*Work with Katie on Bunny Generals
2. What was done?
*Added some helpful features based on Acey's feedback, still need a better outcome from wrong answers rather than a complete reset.
3. Problems encountered?
*I have a lot of homework right now for some reason.
*I wasn't able to meet with Dr. Barnes to show last week, there was no meeting
4. What did you learn this week?
*Quaternions, abstract math elements, that turn your mind into pudding.
5. What's planned for next week?
*Meet with Dr. Barnes, get feedback, meet with Katie get feedback
*We should probably get to work on some sort of documentation, aside from pitch doc.
6. Hours worked.]
*About 8
*Add some stuff to Bunny Generals from feedback
*Get some feedback from Dr. Barnes
*Work with Katie on Bunny Generals
2. What was done?
*Added some helpful features based on Acey's feedback, still need a better outcome from wrong answers rather than a complete reset.
3. Problems encountered?
*I have a lot of homework right now for some reason.
*I wasn't able to meet with Dr. Barnes to show last week, there was no meeting
4. What did you learn this week?
*Quaternions, abstract math elements, that turn your mind into pudding.
5. What's planned for next week?
*Meet with Dr. Barnes, get feedback, meet with Katie get feedback
*We should probably get to work on some sort of documentation, aside from pitch doc.
6. Hours worked.]
*About 8
Subscribe to:
Posts (Atom)