Skip to main content

Access parent"s parent from javascript object



Somthing like







var life= {

users : {

guys : function(){ this.SOMTHING.mameAndDestroy(this.girls); },

girls : function(){ this.SOMTHING.kiss(this.boys); },

},

mameAndDestroy : function(group){ },

kiss : function(group){ }

};







this.SOMTHING is what I imagine the format is, but it might not be. What will step back up to the parent of an object?



Source: Tips4all

Comments

  1. In this case, you could use life to reference the parent object. Or you could store a reference to life in the users object. There can't be a fixed parent available to you in the language, because users is just a reference to an object, and there could be other references...

    var death = { residents : life.users };
    life.users.smallFurryCreaturesFromAlphaCentauri = { exist : function() {} };
    // death.residents.smallFurryCreaturesFromAlphaCentauri now exists
    // - because life.users references the same object as death.residents!


    You might find it helpful to use something like this:

    function addChild(ob, childName, childOb)
    {
    ob[childName] = childOb;
    childOb.parent = ob;
    }

    var life= {
    mameAndDestroy : function(group){ },
    kiss : function(group){ }
    };

    addChild(life, 'users', {
    guys : function(){ this.parent.mameAndDestroy(this.girls); },
    girls : function(){ this.parent.kiss(this.boys); },
    });

    // life.users.parent now exists and points to life

    ReplyDelete
  2. If I'm reading your question correctly, objects in general are agnostic about where they are contained. They don't know who their parents are. To find that information, you have to parse the parent data structure. The DOM has ways of doing this for us when you're talking about element objects in a document, but it looks like you're talking about vanilla objects.

    ReplyDelete
  3. Here you go:

    var life={
    users:{
    guys:function(){ life.mameAndDestroy(life.users.girls); },
    girls:function(){ life.kiss(life.users.guys); }
    },
    mameAndDestroy : function(group){
    alert("mameAndDestroy");
    group();
    },
    kiss : function(group){
    alert("kiss");
    //could call group() here, but would result in infinite loop
    }
    };

    life.users.guys();
    life.users.girls();


    Also, make sure you don't have a comma after the "girls" definition. This will cause the script to crash in IE (any time you have a comma after the last item in an array in IE it dies).

    See it run

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex