Still a bit comfused about.

Epley: Well, either way, you said do***ent.body.

Villani: I ***umed the viewport was scrolling, yeah

Tonelli: Try it on another site

Pinkett: Put do***ent.body.scrollTop in the console

Machtley: Is there a best practice for responsive tooltips? or would you suggest to use a plugin?

Yazzie: The viewport = browser/page window?

Endo: ScrollY is also fine, there’s a lot of things you can do in many ways in dom

Drobny: Zumba_addict: inheriting by prototype doesn’t automatically call the “parent” constructor function for you. that part you do yourself, manually, as you’re doing in your fiddle. so line 20 runs before line 11

Drobny: Zumba_addict: er disregard, i’m too tired, wrong, should not have attempted now ;

Kenngott: Let me remove the debugger and see if it changes

Hoyer: Does anyone have an answer to this question?

Denby: You should move the parent constructor call to the top of the constructor of the child

Drobny: But yea that’d fix your problem

Turick: Nope, it’s still 10. Yup, so this.age on line 20 should be swapped with Cl***B.callthis; Right?

Defusco: I’m not sure why the movement is being odd on this

Bartoli: That means, I really have to be careful what I’m inheriting and what property names I use

Marsch: So am I right that when calling the constructor when creating a child, it should always be the first call?

Davolt: Which is part of why inheritance can be dangerous and confusing

Trueman: I’m not sure if my terminologies are right 😀

Schardt: Here is what I’ve noticed

Goethals: Here is what I’ve noticed after I’ve been running it manually. It constructor is similar to what I was doing in Pascal days where the params sent are updated by the function and are also seen by the caller that sent it. However, I remember add a special symbol before the parameter name

Nothem: It constructor/The constructor

Gentleman: I don’t think Pascal is going to be too relevant

Garley: I’m referring to the inheritance like of Cl***C.callthis

Hutchingson: The this parameter is similar to the pascal parameter when &somevar is used

Arpin: It really is just a function appending values to an object

Golabek: In p***cal function sumsomevar – the somevar will be the old value even if it gets updated on the function. However, if declared as &somevar, it will be sent back to the caller

Brave: Yeah Pikul, that’s what I meant. it’s like extend?

Lechliter: I think extend does similar thing too. Right?

Jauss: I don’t know if extend is a javascript thing or an underscore thing

Anding: For example A extends B. B shouldn’t override properties of A

Pusey: They will be combined

Wzorek: No, A will override B

Verhague: Maybe i’m getting confused with BackboneJS’s extend with underscore’s extend

Schiro: Well, i would think it’s a matter of when you are extending A over B

Huval: Although, i can’t remember if underscore extends or jquery extends do those checks

Mate: Zumba_addict: Cl*** hierarchies? Don’t do that!***-hierarchies-dont-do-that.html See also, !inheritance

Mate: Zumba_addict: JavaScript does not really have “inheritance” like cl***ical languages. What it has is more properly called “property delegation” or “behavior delegation” – ie foo.barbaz when !foo.hasOwnProperty’bar’ is essentially doing, baz

Conroy: Thanks for the links, I’ll read them once i get to my desk. I’m entering the tunnel soon

Defusco: Still a bit comfused about what’s going on with the movement on this . I had the moveX moveY set to just +20 or -20, and then I’ve tried adding an if to make sure that they’re at 0 when a different direction is pressed, but Its not really working and I’m sure it’s something pretty basic.