Coffee Maker

Open source Java-Development classes designed to make Java game development more like Game Maker. Currently has built-in support for:
[]collision-checking
[
]key checking
[]drawing
[
]step
[]begin step
[
]end step
[*]create

As it is open source, it is easy enough to edit. I plan to add in the future:
[]3D Support
[
]Mouse events (just being lazy here)
[*]Anything else?

Download link: www.danielseabra.net/coffee

Pictures of games developed with it:

http://img44.imageshack.us/img44/1145/spscreen.png

http://img573.imageshack.us/img573/7351/cantbelieveit.png

http://a.imageshack.us/img840/9461/screenshotgalleon3.png

Hi

Lots of links are broken on your site. It would be easier to see the changes in the source code if you used a repository and SVN or GIT for example. Do you realize that creating such an equivalent of Game Maker is very ambitious? Good luck.

Edit.: maybe some images are blocked on my machine, it is not your fault.

The idea is to create a stepping stone, not a Game Maker in Java. The interface and the functions are not related at all, just the way of programming. In Game Maker for example one can put a piece of code in the create event of an object. In Coffee Maker you can also do this, like this:

public class something extends GMObject
{
//constructor

public void create()
{
      //code
}

}

Some Java knowledge is needed, but from knowing programming in Java to knowing how to program a game in Java is a big step, and one that I want to make smaller, if possible.

Hi!

I see what you mean and I hope you will get a better result than Game Maker for 3D because I tested a first person shooter using the D3D mode of Game Maker on Gamejolt and it was extremely slow whereas the graphics were rudimentary. However, do not reinvent the wheel. If you plan some 3d support, do not write it from scratch and use an existing 3D engine. I wrote my own 3D engine in 2006 and I can tell you that it requires a huge amount of work. To sum up, I advise you to write your API above an existing engine rather than creating everything from scratch.

Driving game development in Java easier is a good idea but anyway, when something does not work as expected, you feel more comfortable when you know how the low-level layers work and it allows you to be able to repair them.