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

Discussion about the Static keyword

6 posts in this topic

Im sure this keyword applies to many languages. It is the accessing of methods/fields/etc at the "class definition"? level.

I am about to rewrite most of my game after realising that the static keyword is, well, not logical in my case (I think atleast). I wrote many of my classes static - most of these classes were classes that I thought would only be initalized once. Although after realising how easy it would be to just recreate a corrupted object when a corruption occurs (by corruption I mean basically anything, from a multiplayer connection failing, to a incompatable object state) I was like "WHAT HAVE I DONE?".

[b]What are other programmers thoughts on the static keyword in OOP?[/b]

Sure the static keyword can be extremely helpful in certain cases, but in general what do you think?

Thanks,
Xanather. Edited by Xanather
0

Share this post


Link to post
Share on other sites
In general static is useful when used as intended - as a property or method of a class of objects.

Note, you say "at the object level" which is wrong - normal non-static properties and methods are properties of [i]objects[/i]; statics are properties of [i]classes of objects[/i]. You clearly know this already, but it's worth getting in the habit of making the distinction correctly :)

It sounds as though you have fallen into the trap of prematurely constraining your design. While static (and Singletons in particular) are often misused in this way, the problem is with the process of design - [url="http://c2.com/cgi/wiki?YouArentGonnaNeedIt"]YAGNI[/url]
2

Share this post


Link to post
Share on other sites
http://gbracha.blogspot.com/2008/02/cutting-out-static.html

In languages without a good module system (pretty much everything), they are a useful approach for global methods and constants (or near constants) if treated with caution.
1

Share this post


Link to post
Share on other sites
@mrbastard Yeah.. I knew that. [img]http://public.gamedev.net//public/style_emoticons/default/tongue.png[/img] I think I just typed it out wrong. edited. and yes I would admit to a bad design. Probably should have thought it through first. Edited by Xanather
0

Share this post


Link to post
Share on other sites
[quote name='mrbastard' timestamp='1349696266' post='4987954']
In general static is useful when used as intended - as a property or method of a class of objects.

Note, you say "at the object level" which is wrong - normal non-static properties and methods are properties of [i]objects[/i]; statics are properties of [i]classes of objects[/i]. You clearly know this already, but it's worth getting in the habit of making the distinction correctly [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]

It sounds as though you have fallen into the trap of prematurely constraining your design. While static (and Singletons in particular) are often misused in this way, the problem is with the process of design - [url="http://c2.com/cgi/wiki?YouArentGonnaNeedIt"]YAGNI[/url]
[/quote]
Good read by the way thanks :)
0

Share this post


Link to post
Share on other sites
Hi all sure is lots of talk about the static thing. why, why.
I'm Holding all my Game Object Creation and types in a static class.
I did this because Im trying things out. My last game I passed all classes as params and that was a pain Im lazy foo.
So now Im using a ObjectManager Class. Goes something like this.


class cObjManager
{
public:

static vector<obj *>DefinedObj;

cObjManager(){}
~cObjManager(){}

static bool InitObjManager(things)
{
//load all type here and store them in a vector<obj *>
//must allways call this
return true;
}

static obj *CreateNewObj(Params)
{
search static list for the type we want and then create that type and return;
}


};//end class



now all I have to do is add the header to the file I want to use it in.
Call its Inmember once.
And coded like this Obj *newobj = cObjManager::CreateNewObj(Params);

It's so far is saving me time in writing code, looks like its working well so Ill keep going.

Hope that helps.. any way dont not use some part of the language, try it out and find the pittfulls.
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