Screencast : "The dangers of Ext.getCmp()"

[jay@moduscreate.com]

I originally talked about this at the Sencha office on 8/17, but the video angle was not good. So, I decided to do an official screencast on the subject matter.



Questions/comments are welcome.

[FCTim]

Excellent Screencast. Right when I was starting to get fed up with managing various levels of ref's too. Now I have some good alternatives. :-)

[jay@moduscreate.com]

Glad you found some value in it.

Apparently you can hear my wife yelling at my 4 year old around the 15 minute mark. Hooray for good microphones. :-\

[FCTim]

It adds "character" to the screencast.

You should start doing live screencasts about different topics. I'd donate for that cause.

Seriously though, as good as the API doc's are for ExtJS, sometimes it just helps to SEE someone walk through some code.

My two cents,
Tim

[dloew]

Thanx for that great screencast. I never liked using static IDs and tried to avoid it. I have to train beginners using extjs and it's always hard to teach them not to flood the application with Ext.getCmp()-calls. Now I can give them the link to your screencast.

Greetings from Germany

[carl23934]

On this topic, I found a great way to maintain component references in a more "ext-style" way that promotes clean component design.

http://jsjoy.com/blog/123/dealing-wi...-to-components

[jay@moduscreate.com]

On this topic, I found a great way to maintain component references in a more "ext-style" way that promotes clean component design.

http://jsjoy.com/blog/123/dealing-wi...-to-components

Awesome post.