rem: registerChild: function(/*Widget*/widget, /*int*/insertionIndex){ 
add: registerChild: function(widget, insertionIndex){ 
context: 		registerChild: function(/*Widget*/widget, /*int*/insertionIndex){			// summary: record that given widget descends from me			// widget: the widget that is now a child			// inesrtionIndex: where in the children[] array to place it			// we need to insert the child at the right point in the parent's 			// 'children' array, based on the insertionIndex			widget.dojoInsertionIndex = insertionIndex;			var idx = -1;			for(var i=0; i<this.children.length; i++){				//This appears to fix an out of order issue in the case of mixed				//markup and programmatically added children.  Previously, if a child				//existed from markup, and another child was addChild()d without specifying				//any additional parameters, it would end up first in the list, when in fact				//it should be after.  I can't see cases where this would break things, but				//I could see no other obvious solution. -dustin				if (this.children[i].dojoInsertionIndex <= insertionIndex){					idx = i;				}			}			this.children.splice(idx+1, 0, widget);			widget.parent = this;			widget.addedTo(this, idx+1);						// If this widget was created programatically, then it was erroneously added			// to dojo.widget.manager.topWidgets.  Fix that here.			delete dojo.widget.manager.topWidgets[widget.widgetId];		},
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