Tetris Update

Excellent meeting.

Check out the SVN for the 2 source files. PatchTetReload.cpp is the new gameplay functions to work with the graphics a bit easier.  Tetdisplay.cpp is the main function that needs work for OpenAL (audio). main.cpp is the current working source file where the functions from Patch work with (can be easily changed with Tetronimos, but I used this just for my benefit since it holds each individual pieces in the blocks rather then just one coordinate), but that is where the textures need to be worked on.

Most important is to get the textures and audio to work. Take a look at main.cpp for textures, and Tetdisplay.cpp for audio. Besides the OpenGL and OpenAL addons, there’s nothing else to add but the sources (again all gameplay functions I just made them as functions for main rather then a seperate class for ease of use).

For textures:

  •  Get a working texture on screen
  • Work with textures bigger then 256X256
  • Load and properly use JPG, BMP, and PPM files

For audio:

  •  Fix all linking errors between OpenAL and Visual Studio

All that done then the last things we would need are:

  • Add the score text in the boxes.
  • Add Jim’s wonderful flash beginnings to the start of the game.

After all that said and done, we can start throwing out ideas for our next project! Wouldn’t that be fun!

Happy programming!!!

Reason for meetings and Tetris project repo is stale

This is the log info for the src directory in our repo. There have been no changes to it for almost a month? Since I was the last to change it, I know that it was last updated when we had our first meeting at ACCAD in the fishbowl. Can we get the most recent source in the repository please?

Revision: 2
Last Changed Author: goose
Last Changed Date: 2008-01-14 16:57 GMT
Text Last Updated: 2008-01-14 16:57 GMT
Properties Last Updated: 2008-01-14 16:57 GMT

I’ll be more than happy to teach the basics of how to use SVN and when/why to use the tool. I would like to have the few developers checking in designs and updates when the make them and I plan on making a second repository for the website. As it stands there has been a little activity in the group of late. I think that we should think about rethinking why we have meetings and perhaps make live meetings a way to teach new tools, and bring people in to show off what they have done that week. Instead of planning and talking about little things. That can be done on the bulletin board.

The more discussion, even if a little off topic, the better.

Some additions to have made

The purpose of this site is to let everyone have a opportunity to participate. Lurk if you feel the need, but any input or suggestion or a simple salutation is a sign that people are actively interested in what we are doing. I want to make this whole site/group better, and better able to work together in many different ways. I want to make some changes to our system, and to add some tools to our site suite. Some ideas of things that I want and I think would be useful for everyone are:

  • Task assignment list
  • More information on our projects
  • Listing of the groups leadership hierarchy
  • List of technologies we use (perhaps a tool suite)
  • Thank you page and any affiliations
  • Well thought out coding style and project process
  • Some tutorials, and getting started help
  • Help wanted section
  • Project calender
  • IRC channel
  • Wiki

Feel free to tell me what more we should do, or if anything here if useless. I was also thinking of adding a project managment portal, and thats a list of some FOSS versions that I’ve found. I also want to perhaps start some more online activities to generate a more robust community.

Any time you want to talk about GCC related things, post them here or in the BBS. I want questions and discussions to be public, and searchable. This enables more people to be in the know about whats going on and to also learn how we do things. I would like to bring back the weekly online internet chats. It seemed that that was good way for people to interact. If/When I get an IRC channel up, I’ll most likely be a constant in the room, and if a few other people would also agree to man the chat room, we could possibly branch out more easily since newcomers would have a fast and easy way to directly communicate with members.

Thoughts? Ideas?