rem: addChild: function(	/*Widget*/				widget, /*DomNode, optional*/	overrideContainerNode, /*String, optional*/	pos, /*DomNode, optional*/	ref, /*int, optional*/		insertIndex){ 
add: addChild: function(/*Widget*/	widget, overrideContainerNode, pos, ref, insertIndex){ 
context: 		addChild: function(	/*Widget*/				widget, 							/*DomNode, optional*/	overrideContainerNode, 							/*String, optional*/	pos, 							/*DomNode, optional*/	ref,							/*int, optional*/		insertIndex){			// summary:			//		Process the given child widget, inserting it's dom node as			//		a child of our dom node			// overrideContainerNode: a non-default container node for the widget			// pos:			//		can be one of "before", "after", "first", or "last". This			//		has the same meaning as in dojo.dom.insertAtPosition()			// ref: a node to place the widget relative to			// insertIndex: DOM index, same meaning as in dojo.dom.insertAtIndex()			// FIXME: should we support addition at an index in the children arr and			// order the display accordingly? Right now we always append.			if(!this.isContainer){ // we aren't allowed to contain other widgets, it seems				dojo.debug("dojo.widget.DomWidget.addChild() attempted on non-container widget");				return null;			}else{				if(insertIndex == undefined){					insertIndex = this.children.length;				}				this.addWidgetAsDirectChild(widget, overrideContainerNode, pos, ref, insertIndex);				this.registerChild(widget, insertIndex);			}			return widget; // Widget: the widget that was inserted		},
meta: 4707	/local1/tlutelli/issta_data/temp/all_js/javascript/2006_temp/2006/4707/50c3492c4c3c825dbd3401e134a19ed46799c456/DomWidget.js/clean/www/resources/dojo-ajax/src/widget/DomWidget.js