Three opposite declarations of Javascript objects though wholly one seems to work?

I have 3 rudimentary Javascript vigilant definitions in my HTML page. The
initial one works though a others seems to means an blunder on a page. we
am prying to learn to see that proceed is a many common proceed to
announce an vigilant in Javascript and that proceed is a best proceed to
announce an vigilant in Javascript. we have used C++, Java, and a .NET
support work and there seems to be a customary proceed of dogmatic objects
in these forms of OOP languages. we would like to find a proceed that is
customary to announce a objects so that my formula is customary opposing
all of a web pages that we work on. That is we would like to have my
methods and properties all announced in a vigilant during chapter form and
not so many as only supplement them in as one goes that we cruise is
illusory for a many partial from what we have seen in a code.I also
announced an lifeless vigilant that we cruise is correct. var Ball = {};
//Shouldn't this be an lifeless objectQuestion: we cruise that we am not
totally certain what vigilant means in this clarity and how it should be
used in Javascript objects?For example: In Java or C++ a new user creates
a new instance of a object. Like below. category PPP { int temp; } PPP
testobject = new PPP(); The above is how we would emanate an instance of
category PPP in Java though how would this be finished in Javascript seems
opposite since we cruise that a Object keyword is throwing me off here and
there is some reason we review (not certain where) that Javascript is
rather opposite in that all is a duty or something?????Code: