Learning Ext JS to customise dialogs | Community
Skip to main content
New Participant
May 4, 2016
Solved

Learning Ext JS to customise dialogs

  • May 4, 2016
  • 4 replies
  • 2353 views

Having run through the various development articles on customising dialogs and working with XTypes the examples always include sample js file that handles the dialog, and extends functionality when creating a custom XType.

However, I find I get lost in points of the JS code as it is using Ext JS .

Now to fully use Ext JS one needs purchase https://www.sencha.com/products/extjs/newpkg/.

However all I want to do is understand how the examples work in the AEM documentation and be able to create simple extensions to XTypes for my custom components.

If I look for ExtJS tutorials they all lead to http://docs.sencha.com/extjs/6.0/ or a similar page on http://docs.sencha.com

This requires

I can get Ext JS 6.0.2 on a 30 day trial.

 

Is it necessary to purchase Ext JS 6.0.2 for AEM dialog development?

Am I in the right place to learn how to use Ext JS 6.0.2?
 

Regards

Clive Stewart

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Here is an article that may help  http://experience-aem.blogspot.ca/2014/02/aem-cq-56-chain-combo-boxes.html?m=1 and 

4 replies

New Participant
May 5, 2016

smacdonald2008 wrote...

Here is an article that may help  http://experience-aem.blogspot.ca/2014/02/aem-cq-56-chain-combo-boxes.html?m=1 and 

 


Thank you Scott, this article gives a very good example.

New Participant
May 5, 2016

leeasling wrote...

I would re-think how you're structuring your component before you go build a custom xtype.  There is always a way to achieve the functionality you need without going down the rabbit hole that is custom xtypes (not to mention the classic UI will go away and be unsupported).

What's your use case?

 


This exercise is more about me trying to understand how to customize an XType and more importantly - trying to understand ExtJS. So it does not really matter for me if classic UI goes away.

smacdonald2008
smacdonald2008Accepted solution
New Participant
May 4, 2016
New Participant
May 4, 2016

I would re-think how you're structuring your component before you go build a custom xtype.  There is always a way to achieve the functionality you need without going down the rabbit hole that is custom xtypes (not to mention the classic UI will go away and be unsupported).

What's your use case?