• 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
Martin Winged

How to get a reference to a prototype's parent

6 posts in this topic

When I need to pass a function with parameters as a parameter to another function I use a partial function application function, which looks like this:

function wrapFunction(func, params) { // 'params' should be an array
	return function() {
		return func.apply(this, params);
	};
}

This works fine when passing a function like alert(arg), which is not a prototype of any object (as far as I'm convinced). But as soon as I need to pass a prototype function of an object, for example camera.moveTowards(arg1, arg2, ...), argument 'this' in wrapFunction() needs to be replaced by 'camera'. Is there any way to get a reference to a prototype's parent and pass it in place of 'this'?

 

PS: I don't want to add another argument to wrapFunction, which I would declare every time (like wrapFunction(camera, camera.moveTowards, [arg1, arg2, ...])), because it messes up the readability.

Edited by Winged
0

Share this post


Link to post
Share on other sites
I think you can not get the scope from the function reference itself ...
that is what I think I read not long ago and I think it is also what this article says:
http://stackoverflow.com/questions/1550782/how-to-get-the-this-scope-of-a-javascript-anonymous-function
 

Please leave the scope burden to the calling code, they can always use the 'bind' method or something similar.


I have a feeling that the better answer would be how the problem you are trying to solve should usually be solved.
Unfortunately I don't know that. It might help to think about what the places where the functions are invoked have in common ... and what the places where the functions are defined have in common.
Maybe you can work with some kind of data structure that wraps the scope and the function pointer to help with readability.



Readability is a matter of taste. Working with another wrapper makes it clear what happens, but I don't suppose you like that more than the original call to wrapFunction(...):
 
function buildCallback(func, scope) {
    var callback = new Object();
    callback.wrappedFunction = func;
    callback.scope = scope;
    return callback;
}

function wrapFunctionInvocation(callback, params) { // 'params' should be an array
    return function() {
        return callback.wrappedFunction.apply(callback.scope, params);
    };
}

// ... so that you can call the invocation like this:
var moveTowardsCallback = buildCallback(camera.moveTowards, camera);
var moveTowardsFunctionInvokation = wrapFunctionInvocation(moveTowardsCallback, params);

Not even sure if that would work, btw. Edited by DareDeveloper
0

Share this post


Link to post
Share on other sites

The method you have provided, DareDeveloper, still requires to pass the function's 'parent', which is what I'm trying to avoid, because I feel that there should be a simple way to get the reference's origin.

0

Share this post


Link to post
Share on other sites

Yeah, thought that the better readability is not good enough. But like I said, I think there is no way to do that.

All you can hope for is finding a good place (generic, convenient and mostly hidden functionality) for logic that builds an object with the reference to the scope.

 

Btw. you can read about JavaScript Closures ... they might be on topic but I do not get them:

 

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Closures

http://msdn.microsoft.com/en-us/magazine/ff696765.aspx

Edited by DareDeveloper
0

Share this post


Link to post
Share on other sites

I don't know if this applies to your problem, but I often find myself copying 'this' before defining an anonymous function. I'm not a Javascript guru so I'm not sure if this is the right way to do it, but it's the only way I know of.

function bar() {
    that = this;
    foo = function() {
        // bar.this is not in scope, but 'that' is.
    }
}

HTH

0

Share this post


Link to post
Share on other sites

I decided to totally abandon the wrapFunction idea 'cause warping a function just like this:

function(args) { doSomething(args) }

works flawlessly, it's easier to type, easier to understand and generally it's more suitable for me ;]

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