http://games.greggman.com Games, Game Developerment, etc. en-us http://greggman.com/pageparts/rss_banners/banner-022.jpg http://games.greggman.com http://games.greggman.com/edit/editheadlines/2009-11-18.htm Is there a best design for an API? I don't know but I do have my own guidelines for good vs bad design. One guideline I try to follow is that it's good to design an API to make it hard to use incorrectly. Here's a couple of examples I've run into recently. http://games.greggman.com/edit/editheadlines/2009-10-30.htm If you are using Perforce (p4), sometimes you need a way to reconcile a folder. Both P4WIN and P4V have this feature to some degree. The command line p4 does not so here's a small program to do just that. http://games.greggman.com/edit/editheadlines/2009-08-01.htm This is the story of how I spent $345 for a video game, Space Channel 5 part 2. http://games.greggman.com/edit/editheadlines/2009-06-03b.htm I suppose technically this isn't the first O3D game since there are a few in our samples but this is the first O3D game created by a 3d party. The developers said it took them about 5 weeks with no JavaScript experience and no O3D experience. They've clearly got some smart people there. http://games.greggman.com/edit/editheadlines/2009-06-03.htm I gave a presentation at Google I/O about O3D. In it I show getting started creating a small game in about 20 minutes. (the sound cuts out for 30 seconds at 16:48) You can download the a PDF for the slides here. http://games.greggman.com/edit/editheadlines/2009-04-21b.htm You want to know what I've been working on for the last year? This is it! You can learn the details and try some of the demos at http://code.google.com/apis/o3d/ I think it's incredibly awesome but then I'm bias. For me what makes it awesome: