extraCLientlibs not working as expected | Community
Skip to main content
S
supersoftr30476
Level 2
April 20, 2016

extraCLientlibs not working as expected

  • April 20, 2016
  • 1 reply
  • 1735 views

I referred to https://seminars.adobeconnect.com/_a227210/p43ucnv6655/?launcher=false&fcsContent=true&pbMode=normal and tried to created a touch UI component with clientlib named as "test123" , I used same name in my dialog's extraCLientLibs.

But still it's not operating, when I changed the clientlib name to cq.authoring.dialog it worked perfectly fine. This looks bit weird from what stated in video.

Please provide a full fledged working example for creating custom clientlib for my touchUI component dialog, so that the clientlib should be implemented only on specific component, since using clientlib as cq.authoring.dialog makes that clientlibs to work on other touch UI components as well.

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

1 reply

smacdonald2008
smacdonald2008
Level 10
April 20, 2016

Hey  - check out this AEM Touch UI article. It will show you use of a ClientLibs and application logic meant for a Touch UI component dialog: It was one of Praveen;s sample. 

https://helpx.adobe.com/experience-manager/using/creating-touchui-dynamic.html

Hope this helps... 

S
supersoftr30476Author
Level 2
April 20, 2016

This example is focusing on single component, how we can manage multiple components and their multiple listeners?

In clasic dialog, we were having option to declare listeners at field level of dialogs but in touch UI case we've cq.author.dialog clietlibs defined under specific component. But the problem here is in each component wherever this clientlib will be used, all respective js files will be called, can't we've a simpler way to declare js which should focus only on specific component.

smacdonald2008
smacdonald2008
Level 10
April 20, 2016

I am lookngi to see if there is an internal blog within Adobe. MOst of the TOuch UI articles use that clientlib - as its best practice. 

Terms & ConditionsAccessibility statement

Loading footer...