• 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
ATC

The Singleton Pattern: To be or not to be [used]?

80 posts in this topic

[quote name='davepermen' timestamp='1352645783' post='4999916']You want just one: Instanciate just one. You want global access? Make it a global.[/quote]
This is the right spirit. Avoiding useless extra instances of objects and getting the useful objects where are needed are two interlinked rather difficult problems; rather tragically, progressing on the former makes the latter harder.
Good solutions require good design and forethought, and often tedious code, for example lots of parameters and variables to pass objects around or checks of the presence and validity of objects that might or might not have been initialized, not to mention (in many cases) understanding and accepting the price of global variables: obviously the average mediocre programmer is attracted by singletons because[list]
[*]Singletons look clever and legitimate (a tie-wearing design pattern!) without entailing actual design effort. If it shouldn't have been a singleton, you'll find out when it's too late to change your mind cheaply, because you didn't consider different options and contingencies at the proper time.
[*]Accessing singletons allows a strong subconscious denial (or intentional camouflage) that you are using a global variable, and a delusion that what you are doing is technically better (or at least more enterprisey).
[/list] Edited by LorenzoGatti
0

Share this post


Link to post
Share on other sites
[quote name='LorenzoGatti' timestamp='1352882326' post='5000831']enterprisey[/quote]

Increasing visibility is a good thing, and it will surely make us more... visible. To do that we should, uh... develop our strategy and strategize our development. Implement solutions and solutionize implementations. Aggressively.

[img]http://www.dariawiki.org/wiki/images/b/b7/Jake1.gif[/img]

Edgy?
0

Share this post


Link to post
Share on other sites
[quote name='LorenzoGatti' timestamp='1352882326' post='5000831']
[quote name='davepermen' timestamp='1352645783' post='4999916']You want just one: Instanciate just one. You want global access? Make it a global.[/quote]
This is the right spirit. Avoiding useless extra instances of objects and getting the useful objects where are needed are two interlinked rather difficult problems; rather tragically, progressing on the former makes the latter harder.
Good solutions require good design and forethought, and often tedious code, for example lots of parameters and variables to pass objects around or checks of the presence and validity of objects that might or might not have been initialized, not to mention (in many cases) understanding and accepting the price of global variables: obviously the average mediocre programmer is attracted by singletons because[list]
[*]Singletons look clever and legitimate (a tie-wearing design pattern!) without entailing actual design effort. If it shouldn't have been a singleton, you'll find out when it's too late to change your mind cheaply, because you didn't think consider different options and contingencies at the proper time.
[*]Accessing singletons allows a strong subconscious denial (or intentional camouflage) that you are using a global variable, and a delusion that what you are doing is technically better (or at least more enterprisey).
[/list]
[/quote]

What's the price of a global variable?
0

Share this post


Link to post
Share on other sites
[quote name='Dave' timestamp='1352887428' post='5000844']What's the price of a global variable?[/quote]

Loss of access control. (Also violation of dogma.... j/k)

Globals can be reached by parts of the program that have no business reaching them and can result in serious design problems later on. It's a matter of whether or not you're working with people that can't handle the responsibility. Sadly this is a lot of people, from what I hear. Once things get complicated it can become nearly impossible to have reasonable state expectations for something with global accessibility.

That's a good article you got there, Hodge. Edited by Khatharr
0

Share this post


Link to post
Share on other sites
This one is also worth reading: http://tech.puredanger.com/2007/07/03/pattern-hate-singleton/

Cool quote:[quote]First, it is important to separate the “need for one of something in my system” from the “singleton pattern”. It’s perfectly reasonable to want one of something but to avoid using the singleton pattern. In other words, the problem is in the pattern, not in the goal.[/quote]
2

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