Archived

This topic is now archived and is closed to further replies.

A reversed coding style

This topic is 6577 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

If you're writing an engine, it is generally a much better idea to do the core glue code (like file handling, as mentioned in this case) first and then do the rendering afterwards, than to do the opposite. Any programmer that considers not doing the graphics stuff first as "backwards" hasn't written enough code to know better.

The fact is, it's not backwards at all. Writing the renderer first is fine if you just want to play with graphics code, but if you want to make a larger-scale engine, then it makes little architectural sense. The graphics side of an engine is just the visual "front end" to what's going on underneath, so by building everything around the renderer you're tying the engine into that representation, and that kind of thing will only hurt you later.

Don't worry Dragon, it's not reversed at all.

Share this post


Link to post
Share on other sites
I'm writing an engine here and instead of writing core rendering function of the engine, I'm starting on the map loading stuff and then working that way up. Several "programmers" called that method "a fucked up approach". Any comments?

my style:

map file -> map structure -> map rendering

[This message has been edited by Ðragun (edited December 11, 1999).]

Share this post


Link to post
Share on other sites
I believe the official term is "top-down design"

I'd just include a version number in the file header and actually use it in the load routines if I were you.

And stop talking to programmers, talk to system engineers

Share this post


Link to post
Share on other sites