Side kick component load in 6.2

[umeshj24393]

Hi,

To load the component in side kick we have to add  to #cf in url.

By adding #cf tag which script is executing to display its components. where it is placed in crx de.?

I want to implement that without adding cf# tag , the sidekick component is visible, i do not want to add cf# tag in url.

By simple navigating to localhost:4502/content/project/a.html , the sidekick is visible and its component.

Which js files scripts i will have to added to it?

how to do that?

Thanks

[GK-AEM]

Please refer this js file at the below location and might help you.

\apps\cq\ui\widgets\source\widgets\wcm\ContentFinderTab.js

[kautuk_sahni · Accepted solution]

Hi, 

Can you please elaborate your use-case? why do you not want to add cf# to the link ? any specific reason ?

Please have a look this thread that will talk about what all things happens when we user cf# or editor.html in the URL:

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

// 

    Please have a look at the explanation:-  

    Let the URL be:- http://localhost:4502/editor.html/content/we-retail.html   (i.e. http://localhost:4502/editor.html/.... )
    Request processing will start resource resolution, there in the URL they will see that Script to run is editor.html and here in our case it’s a vanity path, to it will result in calling     “/libs/cq/gui/content/editor.html”(actual path of the Script).
    From there the “sling:resourceType” is taking us to “cq/gui/components/authoring/editors/switch”, here the editing part of Touch UI would be catered.
    Similarly for cf# its -> cq/ui/components/widget -> cq/ui/components/widget -> /libs/cq/ui/components/widget/html.jsp

    Here’s one way to look for Resource resolution:

    Head over to http://localhost:4502/system/console/servletresolver
    Enter the request URL and select the appropriate HTTP method (http://localhost:4502/editor.html/content/we-retail.html)
    The Opting servlets will be listed – I think the ‘chosen’ one is on the top…
 

    Here’s another:

    Head over to http://localhost:4502/system/console/requests and clear existing requests
    ‘Edit’ a ‘simple’ AEM site (e.g. navigate to http://localhost:4502/editor.html/content/we-retail.html)
    Refresh the page in #1 and locate your request
    It may happen that the page you are interesting in sends more than 20 requests – perhaps there’s a configuration to increase how many requests are ‘kept’ for analysis but I don’t know of it – instead, what you     can try is to ‘cancel’ the page-load (so that further requests are not sent to the server)
 

    The downside of 2nd method is limited requests can be tracked this way – the upside is that you get a lot more information that the 1st.

I hope this would help you.

Thanks and Regards

Kautuk Sahni