http://honoluluhacker.com/2008/12/17/refactoring-extjs-for-readability/?utm_source=rss&utm_medium=rss&utm_campaign=refactoring-extjs-for-readability Tech, Linux, Rails by Honululu-based Kevin English Sat, 31 Mar 2012 10:51:21 +0000 hourly 1 http://wordpress.org/?v=3.1.2 http://honoluluhacker.com/2008/12/17/refactoring-extjs-for-readability/comment-page-1/#comment-1716 Juan Mendes Mon, 25 Oct 2010 23:03:23 +0000 http://honoluluhacker.com/?p=426#comment-1716 Hello, I think using Ext.getCmp with and id is a bad pattern. Here's why: What if you need to use two of these components on a page? you're out of luck since you're relying on an id. For the example you mentioned, you should have just set the scope of the selection change to be the current panel by passing 'this' as the scope argument. What you have is not that much better than globals, since Ext.getCmp manages a global list of components. Hello, I think using Ext.getCmp with and id is a bad pattern. Here’s why: What if you need to use two of these components on a page? you’re out of luck since you’re relying on an id. For the example you mentioned, you should have just set the scope of the selection change to be the current panel by passing ‘this’ as the scope argument. What you have is not that much better than globals, since Ext.getCmp manages a global list of components.

]]>