var parent={
childCount: 0,
child: {
id:false,
init: function() {
alert(this.id);
parent.childCount++;
this.id = parent.childCount;
alert(”Child ” + this.id + ” Created”);
}
}
}

Calling ‘parent.child.init();’, the first alert produces ‘undefined’ and the second ‘Child 1 Created’. A second call to ‘parent.child.init();’ produces the ‘1′ from above instead of the ‘undefined’ I’m expecting – I realise this is because I’m working with the same object.

However, calling ‘var firstChild = parent.child.init(); var secondChild = parent.child.init()’ produces the same result (as does ‘var firstChild = parent.child; firstChild.init();).

I’ve also tried the ‘new’ operator. But the code ‘var firstChild = new parent.child;’ produces the error ‘parent.child is not a constructor’.

How is this supposed to work?

http://students.50webs.org
http://vpn.50webs.org

무자본으로 수백만원대의 월 안정수입을 확보할 수 있는 사업을 소개합니다.

♣ 사업 특징.

* 누구나, 자본투자가 필요 없어 손해 보는 일 없는 윈윈-사업.

* 장기 안정수입 확보와 노후대책에 적합한 투잡(부업).

* 확보된 안정수입은 일생 지급되고, 자녀에게 상속 됨.

* 통신사업법 개정으로 개인도 할 수 있는 황금알을 낳는다는 꿈의 이동통신사업.

* 온/오프라인 홍보만으로 평생수입누적!!

* 인터넷으로가능하므로 지방에 계신 분도 사업활동에 지장 없는 전국규모 사업.

* 인터넷 사업용 홈페이지(투잡ok) 무료 분양.

♣ 사업내용은 홈페이지의 에서 상세히 들으실 수 있습니다.

* 연락 주시면 성심껏 돕겠습니다.

* 홈페이지에 저의 성명과 연락처가 있습니다.

* 자본투자 없이 내 노력으로 일생의 안정수입을 확보할수 있는 절호의 기회!

* 본사홈피: http://ceoit.co.kr/web/king098/

* 비번1111 허락없이 글올려서 죄송합니다.

* 등록을 원하지 않을경우url주소를 상기 메일로 보내주시면

다시는 올리지 않겠습니다.

I have now solved this in a way I’m happy with – take a look at Classy JSON

I have now solved this in a way I’m happy with – http://www.thomasfrank.se/classy_json.html

Thanks.

I do understand that javascript is prototype based, but most people do not and I like to think in terms of namespaces, classes, members and instances because I am more familiar with it and there is nothing wrong in thinking in a more abstract way. It’s just a mental representation. You can also simulate class based inheritance. I’ve developed a framework in javascript that makes javascript completely object ortiened with namespaces, classes, enums, events, properties, interfaces that can be private, protected, public, static, internal and you can override and overload methods,you can create methods with strongly typed arguments and you have private, protected, public, static, internal methods.

Object literals are actually hard to maintain. It tries to mimic classes but these ‘:’ and ‘,’ just get confusing when the code grows.

Cool to see it getting that much referencing.

Dustin, I commented on your article, as JSON and the OL are not the same. If you add this difference – one is code syntax, the other is a data format – then it’ll be a really good resource going deeper than mine :)

I personally like Object literals, for they ease programming and maintenance very much.

> The following feels more natural and it’s possible to add classes, objects and members
> to existing objects and namespaces:
> instance:
> [...]
> class definition

Probably some people will never understand that the programming language they are dealing with uses in fact prototype-based, not class-based inheritance; that there are no namespaces, classes, members, and instances there, but only objects with different properties.

And non sequitur. Both forms of object definition can of course be combined sucessfully:

function Prototype()
{
// initialization
}

Prototype.prototype = {
// protoype object property definitions
};
Prototype.prototype.constructor = Prototype;

var p = new Prototype(42);

// See also the “scripts” section on my Website.

PointedEars

instance:

var awesome = new Object();
awesome.commonSense=null;
awesome.standardsCompliance="50%";
awesome.init = function (){
// code
}
awesome.doStuff = function(){
// code
}
awesome.doMoreStuff = function(){
// code
}


class definition

function awesome()
{
//constructor
}
awesome.prototype.commonSense=null;
awesome.prototype.standardsCompliance="50%";
awesome.prototype.init = function (){
// code
}
awesome.prototype.doStuff = function(){
// code
}
awesome.prototype.doMoreStuff = function(){
// code
}


add object instance or class definition to an existing namespace, class definition or object instance

namespace.awesome = ....
classDefinition.awesome = ...
objectInstance.awesome = ...