Communication so good!

I realize also that communication was very helpful maybe our email is full thanx to the project but that's the way we know about everything for example this week they saw that it was on perforce the code of the other team of Mexico but it wasn't integrate it, so they let us know and in school we told us of course they already knew but in one class we talk about it and after the integration test it and saw that in generally the sound it was ok (that was the part they had to do) and that had some fun noices, we even discuss about they could give some mexican flavor to the tetris with some popular mexican songs.
So the communication is very important as for today we think we are ok with all the progress we had in the game an is functioning OK.

As the week started!

This last week because the implementation of the keys was OK we did little adjustments to the code and this was because as the week begins we realize that the code wasn't on perforce uploaded maybe it was some mistake or trouble afortunaly we all have a copy of the code sent it by email, so I dispose to uploaded and realize that in only one day or so the code was completed different so the new code didn't compile anymore!! But John came to rescue once again and helped me to integrate again the code with the new changes.
And all was ok again, we even test the game and it was quite fun!

not the right implementation

We achieve this week to put in c++ code what we code in C#, but unfortunely we didn't use GLUT we used Windows Forms because that was the only way we knew of how to implment KeyEvents In the design we didn't realize that had to be in GLUT because we didn't see that the other teams were coding like that, for me it was easiest to use windows forms because all is already pre-fabricated we don't have to worry about the render or painting of any object, and all the expected events are already constructed, I do realize that this type of project is for another means but I would like it to take a chance to see if these capabilitiees already made could function for our project, so when we try to implement it on the baseline project we realized that it can't be because they use GLUT so it was difficult because we had to understand from zero what is GLUT! we don't even know it, but finally John helped us to figure out an it has been a good co-worker for us because guide us for the right track. Montse and Sergio were the heros who achieved implementing to GLUT so we are very thankful to them also. So we hope it's ok the project and had minor bugs and details.

Doing our first lines of code of tetris

Today we had a meeting at school where we started to make a quick draft with some lines of code of how will be the methods for the movement of the blocks of tetris, I made a quick draft in C# for making a better understanding, In my work I develop on C# so it was easy for me coding fast in that language what we needed to represent, later on when we had the idea we passed to C++ but we hadn't enough time so as homework we have to try to make each method of the movement class. Hope everything flow as expected.

Designing doument for Tetris

We upload the designing document for the tetris game is a little vague for my taste in the eventHandler methods because we really don't know how it will be implemented to the block or object that will call this methods so we made like a guess and put the description, hope the next week could like make clearer the design as the implementation, I'm a little exciting about the next weeks how it will result the tetris game and I hope it won't be a mess or a complete caos when we decide to join all the modules.

Our designing for tetris meeting

Today we had a designing meeting with my team b for the design of the key strokes and the events necessary for the movement of the blocks, we finish the meeting with a good design I guess I even make a quick draft that how the code will look like for having a more intuitive way of creating methods. I liked make a design meeting because we all understand how will be coding next and how each method has a relationship with his own class or another.
Productive day.. I say.

Now our turn!!

Ahh! now we have to code it, not quite easy because we are now in the counterpart where we have to understand someone else code, and is funny but eventhough the team that made the design for us is in the same university we didn't program any meeting with them, I think is beacuse we see them in each class, anyway we understand ok the design and some troubles, well several, the thing is that we handle some methods for each of us and when we wanted to join in it in a solution it was a complete mess!! Nothing compile of course because none of us knows to programm in c++ but c'mon we though we read ok the forums and tutorials about coding in c++ but it started to fail when we join the methods so then we realize that it wasn't the way of doing it, so we make another effort for clearing the most errors we had, and eventhough we think we made a good job it was some rare fail at debugging about some memory location, but we couldn't understand what was it, 'till tonight I though it may be like c some sort of calloc and malloc, but it's a little late, it was hard but we learned the lesson.