Chuyển đến nội dung chính

Listeners in CQ (Getting value from one widget into other widget)

Listeners in CQ (Getting value from one widget into other widget)

Problem: While working on a component in CQ I got struck while finding a value from one of the widgets which was to be used in other widget. The solution came with the name "listeners". But how to create one and how to implement it remained a problem.

Solution: In CQ you can associate a listener with a component, a dialog, a widget etc. For that you just need to create a folder with the name listeners as shown below.
As I was looking to use the value in my second widget( title= "SecondWidget") from the first widget( title= "FirstWidget"), I created a listener for it just as shown above with type as nt:unstructured.

I used the property name as beforeshow as I want to do the functionality before showing of that widget. Now just write the functionality under function(){<functionality in pure javascript>}. Thats it you are done.

e.g. function(){alert("123");} in this value will prompt 123 when u will click on the widget.

Extending it further ::
Now in order to get the value we need to use the ExtJs (Javascript Library used in CQ) 
Now as is written in the value of beforeshow "function(){abc(this);}"

On clicking of the second widget the function abc will be called. You can now put this function in any javascript file which is used by your application.
We are passing the widget object along with it by using this.

Here we have used the xtype of widget as "panel" under the parent as "tabpanel". Please see the function below to see the usage.

function abc(tab) {

/* Using the below line you can find any xtype used in the First widget */
// findParentByType is used to get the parent of the panel
// find function is used to get the widget by any of its property we have
// used title in this case
// findByType is used to get children by their xtype (returns array)
var selectionObj = tab.findParentByType("tabpanel").find("title",
"FirstWidget")[0].findByType("selection")[0];

// After finding the select input you can find its selected value by get
// Value function
var val = selectionObj.getValue();
alert(val);
// This value can then be used as the user wishes

// You can also find the Id of the widget by id property
var panelId = tab.findParentByType("tabpanel")
.find("title", "SecondWidget")[0].id;

// You can further use this within document.getElementById function and can
// use normal
// javascript ways to handle it
// Here we have find the select input inside second widget whose xtype is
// not defined
var selectField = document.getElementById(panelId).getElementsByTagName('select');
}

Nhận xét

Bài đăng phổ biến từ blog này

How to add a new supported language in CQ / WEM (Translator in CQ)

Use case:  You want to add new language to CQ Change display language options in translator grid Change language name and default countries  Solution: You can access translator UI in CQ with following URL http://<HOST>:<PORT>/libs/cq/i18n/translator.html Create new language location for Dictionary Go to CRXDE lite (or your favorite JCR browser) and add this structure (assuming /apps/myapp/i18n as a typical location for custom apps): /apps/myapp/i18n [sling:Folder]     - de [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = de     - fr [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = fr Then reload the translator and the path /apps/ myapp /i18n should show up in the drop-down at the top. Note: the translator will only save translations for languages that are actually present underneath the path (e.g. /apps/myapp/i18n), others will be skipped. Then on jsp pa

Login / Logout on a Publish instance and Closed User Group (CUG)

In CQ5 there is the login logout could be configured using a Closed User Group. Closed User Groups (CUGs) are used to limit access to specific pages that reside within a published internet site. Such pages require the assigned members to login and provide security credentials. http://dev.day.com/docs/en/cq/5-4/howto/create_apply_cug.html The logout using /libs/cq/core/content/login.logout.html always gets redirected to the geometrixx site   http://localhost:4503/content/geometrixx-outdoors/en.html By configuring the Default login page  under the osgi configuration for com.day.cq.auth.impl.LoginSelectorHandler to be – /content/mysite/en/login But still after logout the page goes to the geometrixx site. IIRC, the redirect first goes to to / which then goes through the standard, somewhat complex handling of the root with multiple redirects: 1) / has a resource type of sling:redirect and redirects to /index.html 2) /index.html is handled by the RootMappingServlet [0] which h

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene