• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Batzer

Writing a simple Framework

4 posts in this topic

Hey guys,

 

I'm currently trying to write a simple 2D platformer with C++ & DirectX and it is going pretty well, but until now most of the code is in the WinMain of my program, thus it's getting realy hard to maintain. So I want to write my self a little framework to make the code more readable and maintainable, but I don't realy know how to structure the whole thing. My first Idea was to copy the design of XNA, because I like how easy it's to use. The problem is that I ended up having mostly small wrapper-classes that would require to have a getter-function so I could actually initialize the other classes.

As an example:

 

class GameWindow {
public:
    GameWindow(int width, int height, const std::wstring& title);
    HWND GetHandle() const; // I need this to initialize the swapchain
};

class Renderer {
public:
    Renderer(HWND window, int backBufferWidth, int backBufferHeight);

    // Need these to create buffers, shaders etc. and draw stuff ...
    ID3D11Device* GetDevice() const;
    ID3D11DeviceContext* GetContext() const;
};

 

I think these classes are near to useless, as they only initialize stuff and return them via getter-functions so I can actually use them.

So my question is: Do you guys have some useful tips on writing a framework? Or is my approach completely wrong?

 

I hope somebody knows how to help me smile.png

0

Share this post


Link to post
Share on other sites

Yeah I have something similar - a renderer class that pretty much just encapsulates the device.Btw a word of advice - if it "is going pretty well", just stick with it, there isn't a right or wrong way really.Re-coding your framework from scratch is a mistake(speaking from experience).

0

Share this post


Link to post
Share on other sites

You are probalby right. I spend way too much time thinking about how to do things and if it's the right way instead of just getting something finished.

The only problem is that I don't realy have a framework yet. I just put everything in the WinMain. So I guess my problem is that I get stuck the minute real OOP is involved :D

0

Share this post


Link to post
Share on other sites

To be perfectly honest, I think you should create the objects that you mentioned, even if they are simple and just have helper functionality right now.  Once you have the bones of the framework created, then it will grow organically from there - at least that is how my framework evolved (its been running longer than 10 years!).

 

Give it a shot, see what works and what doesn't, then improve it and repeat.  You learn a ton this way, and you can make it work how you want it to.

0

Share this post


Link to post
Share on other sites

It becomes easier to maintain the code if you make your reusable engine in C++ and then call it with game specific code in a more safe language with garbage collection. I would not want a common mistake in a game prototype to crash the core of the engine from poor memory protection.

0

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  
Followers 0