[CLOSED]Ext IDs

[LesJ]

Ok... when do you use the IDs of the DOM elements?

I inspect them visually and this gives me more info about the widgets. I can quickly understand or learn the application if the IDs are informative and consistent.

I assume tools such Illuminations for Firebug could parse the ID and generate even more useful info.

[mitchellsimoens]

Easy way to visualize components... if you open firebug (or the like) and mouse over DOM elements, it will highlight it. No change required for that.

[LesJ]

Easy way to visualize components... if you open firebug (or the like) and mouse over DOM elements, it will highlight it. No change required for that.

I use Illuminations. This works great, but only in Firefox.

Take a look at Ext css class names - they are consistent and informative.

The effort to correct the generated ID names is miniscule, but better names would provide helpful information.

[mitchellsimoens]

I'm gonna stop posting here... this is a none issue.

[evant]

I don't really see this as being much of an issue, though I guess it might be something we could look at eventually.

However I wouldn't say the amount of effort is miniscule, there's many more important things to look at now.

[LesJ]

Ext.Component's getId() changes between releases:

// Rel 3: As you can see the ID is not very informative.
// It's just a prefix + sequential number.
getId : function(){
	return this.id || (this.id = 'ext-comp-' + (++Ext.Component.AUTO_ID));
}

// Rel 4: This is better b/c the ID includes the xtype prefix.
getId: function() {
	return this.id || (this.id = (this.getXType() || 'ext-comp') + '-' + this.getAutoId());
}

// My suggestion:
// Modify this method to have the "ext" or "x" prefix,
//   so it sorts nicely in the Ext widget registry.
// This is a small change that provides further improvement to the ID format.
getId: function() {
	return this.id || (this.id = 'ext-' + (this.getXType() || 'comp') + '-' + this.getAutoId());
}