If I was to add additional levels (with different brick layouts) to the program, what would be a good aproach? 1 method per level?
The same for bricks. If I was to add different kinds of bricks (in size, in shape - squares, tetris forms, etc), how/where should I code them? A method? A class?
3) Sofar I've used the bounding box method myself. If that is too course however, then use the distance, radius and angle of approach of the ball(s) to determine whether there is a collision between balls or ball/brick. That complicates the formulas, so, as you said, if it is not a big problem, I would leave that for now.
Knute Snortum wrote:An Applet, huh? Those aren't used outside of the classroom, so redoing the code in Swing or JavaFX would make sense. I'd vote for JavaFX, but there is some differing opinions on that.
Piet Souris wrote:Looks nice! Is it true that the ball slows down (to us, spectators), when it approaches the event horizon? ;)
No matter. Try again. Fail again. Fail better. This time, do it with this tiny ad:
global solutions you can do at home or in your backyardhttps://www.kickstarter.com/projects/paulwheaton/better-world-boo