Forum Discussion
PerBonomi - Absolutely, it is possible, you'd need some javascript code to do this for you. e.g.
Custom Component 1 <div class="custom_comp1"> //your links which will swap the component goes here <a href="#" class="swap_link">Click to swap</a> // the jQuery code goes here, which will swap the content from CC2 on click of the link. You can include the CC2 on the same page here and keep it hidden, and on click of the link in CC1, hide the CC1 and show CC2. <script> $('.custom_comp1 .swap_link').click(function(){ $('.custom_comp2').show(); $('.custom_comp1').hide(); }); </script> </div> Custom Component 2 <div class="custom_comp2" style="display:none;"> //CC2 content goes here </div>
I hope this helps.
- PerBonomi11 years agoBoss
Thanks for that. Usually that would be a good way to do it.
My "problem" is that the second custom component in question uses a freemarker macro to do a large api call and I don't want to do that call unless I specifically load the second component.
- VarunGrazitti11 years agoBoss
PerBonomi - In that case, you can create an Endpoint instead of your CC2, and make an ajax call to that endpoint from CC1. This would load the content on click rather than show/hide and would save your API call unless the user clicks.
- DougS11 years agoKhoros Oracle
If you use an endpoint, you can share code between your components and endpoints by including them in a "macro" file (you can create macros through the endpoints tab in Studio).
If you find that you really need to render a component of some kind (and not an endpoint), we do have these javascript functions you can call to render components dynamically via JavaScript:
/** * Renders a component in place. * * @param componentId (String) The ID of the component to render. * @param data (Object) An object literal that can contain key/value pairs that will be passed as parameters to the component. * @param ajaxOptions (Object) An object literal that will be used to extend the XHR transport object. The "success" and "error" functions cannot be provided since they are used to render in place. * @param clientId (String) ID of element where the component should be rendered. If not specified then document.write will be used to write out the component in the current location of the script tag that contains this directive. */ LITHIUM.Components.renderInPlace(componentId, data, ajaxOptions, clientId);
/** * Renders a component. * * @param componentId (String) The ID of the component to render. * @param data (Object) An object literal that can contain key/value pairs that will be passed as parameters to the component. * @param ajaxOptions (Object) An object literal that will be used to extend the XHR transport object, typically used to define a "success" callback function. */ LITHIUM.Components.render(componentId, data, ajaxOptions);
-Doug
Related Content
- 10 years ago
- 4 years agoInactive User