Sign in to follow this  
beebs1

Design Question

Recommended Posts

beebs1    398
Hiya, Every time I try to come up with a good design for an engine, I end up with a top-level 'Engine' interface/class. I really don't like this, as it means that all the engine components are very tightly coupled. Without this 'manager' to hold everything together, the coupling is much better but I can't see a way of doing some things - like having the engine run different subsystems on different threads. I've looked through these forums, but everyone seems to use the 'Engine class' method. I was wondering if anyone could suggest a better design, maybe something that has worked for them in the past? Many thanks for any help [smile]

Share this post


Link to post
Share on other sites
SiCrane    11839
If you try designing an engine, then it's pretty much a given that you're going to end up with an engine class. After all, wouldn't you think it was pretty strange if you tried modeling a toaster and didn't end up with a toaster class? If you want to get rid of the engine class, try designing a game rather than an engine.

Share this post


Link to post
Share on other sites
helix    301
I would argue that it's better to build your game ontop of your engine rather than take the engine out of the archetecture completely (if that's what you were suggesting). Just don't couple your engine components. Make sure they are modular.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this