Hi,
I did it with the CMSViewer selecting multiple classes and some hacking in a stylesheet, where the infosheetcollection is a container-only. Issue is that using a string[] for multiple classnames makes it impossible to use a custom order (passing the 'order' parameter gives an Exception because the collection doesn't have custom fields:
Basically it does this:
string[] classnames = new string[] {
"vitsol.infosheet",
"vitsol.infosheetcollection"
}
CMSViewer viewer = new CMSViewer();
viewer.SelectNodesClassNames = classnames;
viewer.TransformationName = classnames[0] + ".categorized";
viewer.SelectNodesPath = path;
viewer.ViewMode = CMSViewerViewModeEnum.MultipleItems;
viewer.SelectNodesOrderBy = order;
viewer.SelectNodesMaxRelativeLevel = 3;
the stylesheet looks like this:
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:vitsol="http://www.vitronics-soltec.com/extensions"
exclude-result-prefixes="vitsol"
extension-element-prefixes="vitsol">
<xsl:output method="xml" version="1.0"
indent="yes" encoding="utf-8"
standalone="no" omit-xml-declaration="yes"/>
<xsl:strip-space elements="*"/>
<xsl:template match="vitsol.infosheetcollection">
<xsl:variable name="NodeID" select="NodeID"/>
<ul class="infosheets">
<li class="folder"><a href="{vitsol:MapAlias(AliasPath)}"><xsl:value-of select="NodeName"/></a>
<ul>
<xsl:for-each select="../vitsol.infosheet[ParentNodeID=$NodeID]">
<li class="infosheet">
<xsl:call-template name="vitsol.infosheet"/>
</li>
</xsl:for-each>
</ul>
</li>
</ul>
</xsl:template>
<xsl:template name="vitsol.infosheet">
<a href="{vitsol:MapAlias(AliasPath)}"><xsl:value-of select="InfoSheetNumber"/>. <xsl:value-of select="InfoSheetTitle"/></a>
</xsl:template>
<xsl:template match="vitsol.infosheet"/>
</xsl:stylesheet>