Subject: Data Ranges From: Charlie Kaiman <ckaiman@xxxxxxxxxxxxxxx> Date: Fri, 28 May 1999 15:35:17 -0400 |
Hello, I was wondering if someone could tell me whether or not there is a way to limit data ranges using XSL? For instance, I am populating the following TABLE using an ASP Recordset: <xsl:template match="products"> <TABLE CLASS="inner" CELLSPACING="1"> <TR> <TD><DIV onClick="sort('name')">Product Name</DIV></TD> <TD><DIV onClick="sort('name/@url')">Product ID</DIV></TD> <TD><DIV onClick="sort('pending')">Pending</DIV></TD> <TD><DIV onClick="sort('authorized')">Authorized</DIV></TD> <TD><DIV onClick="sort('published')">Published</DIV></TD> </TR> <xsl:for-each select="product" order-by="name"> <TR> <TD><DIV><xsl:element name="a"><xsl:attribute name="href"><xsl:value-of select="name/@url" /></xsl:attribute><xsl:value-of select="name" /> </xsl:element> </DIV></TD> <TD><DIV><xsl:value-of select="name/@id" /></DIV></TD> <TD><DIV><xsl:choose><xsl:when test="pending[. != 'empty']"><xsl:element name="IMG"><xsl:attribute name="SRC"><xsl:value-of select="pending" /> </xsl:attribute> </xsl:element> </xsl:when> <xsl:when test="pending[. = 'empty']"> <DIV> </DIV></xsl:when></xsl:choose></DIV></TD> <TD><DIV> <xsl:choose> <xsl:when test="authorized[. != 'empty']"> <xsl:element name="IMG"><xsl:attribute name="SRC"><xsl:value-of select="authorized" /> </xsl:attribute> </xsl:element> </xsl:when> <xsl:when test="authorized[. = 'empty']"> <DIV> </DIV></xsl:when></xsl:choose></DIV></TD> <TD><DIV><xsl:choose> <xsl:when test="published[. != 'empty']"> <xsl:element name="IMG"> <xsl:attribute name="SRC"> <xsl:value-of select="published" /> </xsl:attribute> </xsl:element> </xsl:when> <xsl:when test="published[. = 'empty']"> <DIV> </DIV></xsl:when> </xsl:choose></DIV></TD> </TR> </xsl:for-each> </TABLE> </xsl:template> Everything works great, except for the fact that I get a table that is 100+ rows long. Does anyone have any advice for me as to how I can limit the size of this table to 50 rows per page, using XSL on the client-side? Is there a better way? For instance, should I somehow rely on ASP to define my data ranges, and somehow work with the data that way? I guess this would fall along the lines of *chunking* XML???? Any advice/insight would be greatly appreciated. Charlie Kaiman i3solutions, Inc. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Leventhal's challenge misses th, Paul Tchistopolskii | Thread | Re: Data Ranges, Dieter Maurer |
Re: Leventhal's challenge misses th, Nicolas Pottier | Date | How to Handle Special Characters?, Hari Yerram |
Month |