Comments on: Designing a Tetris Clone: Part 1 http://www.terminally-incoherent.com/blog/2007/10/20/designing-a-tetris-clone-part-1/ Utterly random, incoherent and disjointed rants and ramblings... Wed, 03 Dec 2008 03:41:02 +0000 http://wordpress.org/?v=2.0.5 by: Luke Maciak http://www.terminally-incoherent.com/blog/2007/10/20/designing-a-tetris-clone-part-1/#comment-6646 Mon, 22 Oct 2007 19:54:54 +0000 http://www.terminally-incoherent.com/blog/2007/10/20/designing-a-tetris-clone-part-1/#comment-6646 Oooh! Nice. I didn't actually know about that framework. That's something I could use for the future. It goes on my bookmark list. :) Heh, since I'm also a Java guy I was thinking on branching out on this project and using something else. We'll see though. :) Oooh! Nice. I didn’t actually know about that framework. That’s something I could use for the future. It goes on my bookmark list. )

Heh, since I’m also a Java guy I was thinking on branching out on this project and using something else. We’ll see though. )

]]> by: Dax http://www.terminally-incoherent.com/blog/2007/10/20/designing-a-tetris-clone-part-1/#comment-6645 Mon, 22 Oct 2007 19:26:53 +0000 http://www.terminally-incoherent.com/blog/2007/10/20/designing-a-tetris-clone-part-1/#comment-6645 Being a Java guy I'd go with Java. While I have experience working with Java2D, I would look into using the Slick framework that Kevin Glass wrote (<a href="http://slick.cokeandcode.com/" rel="nofollow">link</a>). When I started with Java2D I found the tutorials on his site. Over the past year or so, I have watched his framework grow. I haven't used it yet due to the lack of time to start a new project, but have had a chance to look at the API and documentation and it is pretty nice. "Good design should work in any OO language - and once we pick one, we can do necessary adjustments if needed." I really wish other developers would read and understand this. Too often I find that people pidgeonhole themselves into one language and tend to design with only that language in mind. I like the approach that you're taking and designing without the language/framework in mind. I wish more people would take that approach. Being a Java guy I’d go with Java. While I have experience working with Java2D, I would look into using the Slick framework that Kevin Glass wrote (link). When I started with Java2D I found the tutorials on his site. Over the past year or so, I have watched his framework grow. I haven’t used it yet due to the lack of time to start a new project, but have had a chance to look at the API and documentation and it is pretty nice.

“Good design should work in any OO language - and once we pick one, we can do necessary adjustments if needed.”

I really wish other developers would read and understand this. Too often I find that people pidgeonhole themselves into one language and tend to design with only that language in mind. I like the approach that you’re taking and designing without the language/framework in mind. I wish more people would take that approach.

]]>