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

[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...

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...