Comments on: Writing a Big Application in Ext (Part 2)

By: yyeshua

yyeshua — Wed, 06 Apr 2011 22:02:29 +0000

Hi. Nice work, that helpme much.

So, I have a question.

How can I call a parent listener (like keypress) when that listener has be overwritten?

Thanks.

By: Saki

Saki — Mon, 23 Aug 2010 20:36:42 +0000

Thanks, I’ll take a look and update the post if it really works in 3.2.x

By: Gjslick

Gjslick — Sun, 22 Aug 2010 00:34:01 +0000

Hey Saki, thanks for this great article. It really got me going on extending Ext’s classes.

I just wanted to give an update about the last section in this post about listeners. As of (I believe) Ext 3.2.0, you can now add a listeners property inside of initComponent(). This is due to Component.initComponent() duplicating Observable’s constructor for this very purpose (probably from so many people writing their own pre-configured classes!)

By: Relexx

Relexx — Fri, 13 Mar 2009 07:02:44 +0000

Thanks for this Saki. I am a complete convert to xtype and lazy instantiation. It makes my code more readable and easier to configure.

By: Bill Hutten

Bill Hutten — Wed, 25 Feb 2009 13:58:19 +0000

Saki: Thanks very much for these clarifications. We\\\’re working on a medium-sized ExtJS application (~14K lines right now, about 1/2 done), and are using pre-configured classes extensively. They\\\’ve worked very well for us.

By: Saki

Saki — Wed, 04 Feb 2009 20:42:20 +0000

@Rostislav,

thank you very much for sharing your practical life experiences with extended classes here. I wish you good luck with them in the future.

By: Rostislav Siryk

Rostislav Siryk — Wed, 04 Feb 2009 18:27:55 +0000

Saki, I want to share my experience here.

Initially, I\’m a Flex developer, but Big Client came to our company asking for ExtJS expert for developing Outlook+Gmail+IM alternative to be used in their intranet as info sharing application.

We agreed, I\’ve heard about ExtJS and even run a couple of samples year ago.

And then project started, I was very quickly learning ExtJS and was shooting my legs again and again, because all the JavaScript and JSON are so hacky for the ActionScript3 developer, who have compiler for all error checking, strict typing, and all static language comfort.

Important moment, we use SCRUM for the development, and very tight deadlines.

And then I\’ve discovered your patterns and learned a lot in one moment. I can\’t say it prevented me from making new errors, but your approach cleared a lot of questions, so now 2 months of development are gone, and I can say application is more or less stable, could be extended and supported further.

I want to thank you for the great work you\’ve done, and all the inspiration of your samples.

Regarding pitfalls, yes, I had it once, the one with listeners, which lead me to setting listeners in “onShow” method, but then I looked into your greatly documented code again and found my mistake.

Thank you!

By: Sey

Sey — Wed, 04 Feb 2009 01:49:40 +0000

Thank you for the great article!

By: Franjanko

Franjanko — Tue, 03 Feb 2009 18:00:19 +0000

Just wanted to say that I\’ve followed the part one of this article for developing a very big extjs front-end (60k~ lines of javascript) and I wouldn\’t have been able to organize the code so well without your suggestions.

I\’ll definitely follow the rules on this second part, and look forward for the third!!!

By: Saki

Saki — Tue, 03 Feb 2009 09:12:45 +0000

@Robert,

please read it again. I’ve written “what the code does”, not how does it do it.

And, sorry for being harsh, if a developer is not able to deal with complexity of contemporary software, if he is not able or willing to understand his own job, then it would be better if he found another job.