• 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.
  • entries
  • comments
  • views

[Structure] When To Seperate Classes and Functions?

Sign in to follow this  
Followers 0


In the programming world (Object Oriented and Procedural) there is this meta-cognitive idea that if a class or function is too big, we should divide it into smaller classes and functions. From this spawned the basics of procedural programming. This way of thinking carried over to object oriented programming in the form of the Single Responsiblity Principle and more Principles I can't name.

So, when do you know when a class is too big? The single responsiblity principle nails it, however to me there seems to be a fuzzy line. The single responsibilty principle says every class should have one responsiblity. In my pong example, I had a GameLogic and GameDraw class to seperate these componets of my program. But imagine this: If my paddle stores it's own sprite, why don't I just have the Paddle draw my Sprite? Surely that won't interfere with handling the GameLogic!

However I kept the single responsibility principle? Why? Because without that line between what's doing what, my code would become extremely confusing. And like I said in my pong example, I want to make sure a change in my GameLogic doesn't mess Up GameDraw. Well, since the Paddle class' responsibility is to handle it's own logic, that means that making a change to my Paddle class' logic can affect how I draw the paddle. And even though I know I probably won't change the Paddle class, it's best to make sure that no matter what I'm keeping my code clean and expansive.

So back to the topic of seperation. There should be seperation between classes, since they should have one responsiblity. When you start getting into more detailed programming, we have to bring in composition. What's composition? Composition is idea that a class is "made-of" rather than "is a". However a class can be both.

If there's ever a blurry line for you, try thinking about what your class is made of and if anything in it should be it's own object. Likewise, if my Paddle Had four floats instead of a normal Rectange, I should create a new class called rectangle that my class is "made-of". My Paddle class is made of an image, a sprite, a position (Vector2f if we want to get more detailed ), and not much more. My Paddle isn't "made-of" a ball, so when I handle collision detection in my paddle I pass in a ball to the CheckCollision() function. You should always make sure the objects in your class make up the class, rather than the objects in your class being what the class uses.

I hope you enjoyed this, and if you don't know what my pong example is, you can find it here: Pong Example!

Sign in to follow this  
Followers 0

1 Comment

A proper object-oriented design requires you to think about much more aspects than just the cohesion of your classes, cohesion is just one small but important matter to take into account.

I suggest you and anyone who's serious about object-oriented programming to have a look at the GRASP guidelines (GRASP = General Responsibility Assignment Software Principles). A short overview can be found on wikipedia: [url="http://en.wikipedia.org/wiki/GRASP_(object-oriented_design"]http://en.wikipedia....oriented_design[/url][url="http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)"])[/url]

These guidelines allow you to make better decisions on how to structure your classes and your entire program structure.

Share this comment

Link to comment

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