We have the below structure in classic UI:
comp1: xtype: cqinclude
path: /apps/thf/components/........./comp2/dialog/items/items/tab1.infinity.json
comp2:
xtype: panel
Finding problem in converting it to respective touch ui dialog.
Any suggestions?
Solved! Go to Solution.
Views
Replies
Total Likes
The cqinclude xtype has been ported in Touch UI , see the "include" component at [1].
See an example at /libs/wcm/core/content/sites/jcr:content/body/account
Property "path" is essential, the "resourceType" property is optional but allow to force the RT for the included path .
Alternatively if you are trying to use in list with the legacy structure, Make use of "datasource" property to generate the list dynamically from the old node structure.
Take exemple on how it's done on the foundation page properties dialog : /libs/foundation/components/page/cq:dialog/content/items/columns/items/tabs/items/advanced/items/section1/items/language/datasource .
The language list is generated by the /libs/cq/gui/components/common/datasources/languages/languages.jsp .
You can do something similar .
Views
Replies
Total Likes
The cqinclude xtype has been ported in Touch UI , see the "include" component at [1].
See an example at /libs/wcm/core/content/sites/jcr:content/body/account
Property "path" is essential, the "resourceType" property is optional but allow to force the RT for the included path .
Alternatively if you are trying to use in list with the legacy structure, Make use of "datasource" property to generate the list dynamically from the old node structure.
Take exemple on how it's done on the foundation page properties dialog : /libs/foundation/components/page/cq:dialog/content/items/columns/items/tabs/items/advanced/items/section1/items/language/datasource .
The language list is generated by the /libs/cq/gui/components/common/datasources/languages/languages.jsp .
You can do something similar .
Views
Replies
Total Likes