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

Java Technique: Using static inner class for debug purposes, then bring it out as a independent class for release

4 posts in this topic

This is merely a discussion of a technique I came up with, and I wanted to talk about it before I really take it far.

Suppose you wanted to create a new object. Instead of having to create a new Java file, we can just create a static class inside of an outer class, and treat the static class as a new class. For example, I have a Foo class, and I need a new Object. I can just go ahead and add a static class Bar inside Foo, like this:

[source lang="java"]//Outer, regular, independent class
public class Foo {
//Inner, temporary class used for debugging.
static class Bar {
//...
}
}[/source]
I could then treat the Bar class as a independent class for Foo. A basic rundown looks like this:

[source lang="java"]public class Foo {
//We treat this as a class of its own.
private Bar bar;
//WRONG, we don't want to do this. We do not try to link it to Foo:
//private Foo.Bar bar

static class Bar {
//Basic rundown on making Bar useful.
private boolean code;

//Setter
public void setCode(boolean value){
code = value;
}

//Getter
public boolean getCode(){
return code;
}
}

//Initialization
public Foo(){
bar = new Bar();
}

//How we obtain the Bar object. Again, we don't link it to Foo.
public Bar getBar(){
return bar;
}

//WRONG, we don't want to do this:
//public Foo.Bar getBar() {...}
}[/source]

And this how we execute Bar as a demonstration:

[source lang="java"]public static void main(String[] args){
Foo foo = new Foo();
foo.getBar().setCode(true);
boolean test = foo.getBar().getCode();
//...
}[/source]

Thus, I have shown you the technique. From here, we can continue to test and debug, and when the Bar object is useful enough, we can then bring it out as a independent class (and giving it its own Java source file). A few questions:[list=1]
[*]Is this technique useful enough?
[*]Would you use it? Why?
[*]How would you use it?
[/list]
0

Share this post


Link to post
Share on other sites
Why is it difficult to create a completely new, independent class in Java? Personally, I think you'd be better off making it simpler to create new classes than developing techniques to work around how troublesome it is.
0

Share this post


Link to post
Share on other sites
I don't really understand how this is related to debugging. It sounds like you use this technique to prototype designs quickly.
0

Share this post


Link to post
Share on other sites
[quote name='rip-off' timestamp='1353609919' post='5003292']
I don't really understand how this is related to debugging. It sounds like you use this technique to prototype designs quickly.
[/quote]

Is that how I should describe this technique? Yes, I believe, I just don't know how to describe it prior to your post.
0

Share this post


Link to post
Share on other sites
I can understand not using, for debug purposes, methods (as the JVM debuggers code hotswap facilities is unable to change class structure). But I really don't see how this technique make it easier to debug.

Just create the new class on its own source code, if the class turn out to be worthless, delete it ;) my 2 cents
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