Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: [CLOSED]Ext IDs

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #11
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    1,909
    Vote Rating
    544
      0  

    Default

    Quote Originally Posted by mitchellsimoens View Post
    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.

  2. #12
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,411
    Vote Rating
    1290
      0  

    Default

    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.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #13
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    1,909
    Vote Rating
    544
      0  

    Default

    Quote Originally Posted by mitchellsimoens View Post
    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.

  4. #14
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,411
    Vote Rating
    1290
      0  

    Default

    I'm gonna stop posting here... this is a none issue.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  5. #15
    Sencha - Ext JS Dev Team evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    18,425
    Vote Rating
    858
      0  

    Default

    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.
    Evan Trimboli
    Sencha Developer
    Twitter - @evantrimboli
    Don't be afraid of the source code!

  6. #16
    Sencha Premium User
    Join Date
    Nov 2010
    Location
    Chicago
    Posts
    1,909
    Vote Rating
    544
      0  

    Default [REOPEN] Ext auto-gen ID format

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

    Code:
    // 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());
    }

Page 2 of 2 FirstFirst 12

Similar Threads

  1. Replies: 3
    Last Post: 16 Aug 2009, 11:37 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •