Assign multiple rendering scripts to a draggable component

One approach would be to simply build a component with that has an edit dialog that allows the author to choose either the grid display or the list display. Or have it use one display by default if the author has not chosen one.

The problem here is that there is no distinct way for you to detect that a page is product page or a suppliers page. Another method is to add a product/supplier radio field to the page properties dialog. The author would specify which type of page is desired and your component could use this page property to determine how to display.

I think what he means with having the component listen to the template is that the template needs to set some properties for the page which the component will "read" eg.
Template 1 (for the products page):

<% pageContext.setAttribute("pagetype","products"); %>

Template 2 (for the suppliers page):

<% pageContext.setAttribute("pagetype","suppliers"); %>

Then the productlist.jsp could simple read that property like:
 

<c:choose> <c:when test="CHECK FOR EITHER SUPPLIER OR PRODUCTS"> //Include the corresponding script (view) here </c:when> <c:otherwise> //Include the other  script (view) here </c:otherwise> //Add more variants in the future </c:choose

and then just include your different sub-scripts or views for displaying the list. This is quite similar to the original list component which you could look at as a reference. Good luck :)

 The way i was implementing is by adding a custom property for templates which i'm using back in my component.jsp to switch the rendering scripts . Looks like the best way may be on the similar lines . Thanks for your replies guys .

Hey Guys ,

  Thanks for your replies

  Right now I'm following the approach which is similar to the one suggested by Andy but wanted a different approach on it . Lets say if the same component has to be displayed in a table approach in a different page i have to again configure the dialog for the component  . 

Justin when you mentioned two templates , how is that the change of the template can be recognized by my component ? I mean any sling way to recognize it ? I'm asking this because , in future if I come across a requirement to display the same component in a table way , I would like to just create a script at the component level 'Products.table.jsp'  and using sling (adding extns or selectors .. )it would pick up this script for rendering the component rather than controlling the logic for switching the scripts embedded in any jsp  . Would any such approach be possible to control the display of a component in a particular portion of a web page ?

[quote:postID=forum__wizo-hey_cqers_iwou__yl7s-since_a_templatedoe]

Since a template doesn't actually contain executable code, this isn't possible. Perhaps you mean setting these attributes in the page component, but that is a bit heavyweight IMHO as it requires creating a new page component.

What I was actually suggesting is to look at the cq:template property of the currentPage.

[/quote]

Ah yes, good point there Justin. I meant the page connected to the template.
And I totally agree on that it would be a bit overkill.. The template properties are probably the way to go :)

Your component would need to have logic in it to look at the template of the containing page. If you wanted to have multiple scripts (which would probably be a good idea from a code management perspective), your main productlist.jsp could just do an include of the appropriate selector-based script.

Since a template doesn't actually contain executable code, this isn't possible. Perhaps you mean setting these attributes in the page component, but that is a bit heavyweight IMHO as it requires creating a new page component.

What I was actually suggesting is to look at the cq:template property of the currentPage.