Home » Forums » AgateLib » Agate Development

GameWindow

Submitted by Agon on Sun, 08/16/2009 - 09:20

Hello,

what about a GameWindow class which stores GameObjects.
The GameWindow would draw only visible (inside the view) GameObjects.
It could be an alternative to AgateApplication which targets games instead of applications.
Also the GameObject could handle more than just a position in eg. a world.
For example physic/network related updates/variables....

‹ Capability checking suggestion (insiped by Axiom 3D engine) Congratulations and two simple suggestions ›
#1Submitted by Agon on Mon, 08/24/2009 - 14:30.

Yeah, AgateGame is a better

Yeah, AgateGame is a better name and your right about the customization on the client side.
Maybe a solution would be to use interfaces or abstract classes for GameObjects.

#2Submitted by kanato on Mon, 08/24/2009 - 10:08.

GameWindow really is what

GameWindow really is what AgateApplication is. It would probably be better to rename that to AgateGame. I've thought about implementing a scene graph like that, but it always seems like such a thing would need to be extensively customized by the client application, so it doesn't seem all that useful. But maybe I am wrong...