This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Column Ordering Design Question
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Column Ordering Design Question
- From: "Chris Bayes" <chris at bayes dot co dot uk>
- Date: Tue, 11 Sep 2001 07:25:40 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
Lou,
Have a look at the beer filtering tutorial on my site section 5 should
be close to what you want. Modify it a little by passing in a comma
separated list of columns in the order you want. i.e <xsl:param
name="columnOrder" select="1,2,3,4" />
Then in the beer template do something like
<xsl:variable name="dot" select="." />
<tr>
<xsl:for-each select="xx:tokenize($columnOrder, ',')">
<td><xsl:value-of select="$dot/*[.]" /></td>
</xsl:for-each>
</tr>
Ciao Chris
XML/XSL Portal
http://www.bayes.co.uk/xml
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of L Rutker
> Sent: 10 September 2001 15:00
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] Column Ordering Design Question
>
>
> Hi,
> I have a question about the proper way to implement the following:
>
> 1)allow customers to select the columns that they want to
> see. 2)Select the order of columns.
>
> My question is how do we control the users pref for column
> numbers and
> ordering. The columns get language specific headers from the
> presentation
> server (added to the original XSL in an XSL > XSL tarnsform)
> while the
> column data comes from the data server.
> What we thought of doing is use JSP tags in the XSL (all XSL
> "components"
> for a page are included in a JSP page) to control the
> ordering of XSL. This
> leads to messy code and a mix of XSL presentation layer in
> JSP tags. (the
> requirement for tags exists regardless to allow us to
> selectively "cut out"
> parts of the XSL based on the users entitlement). These XML
> format tags are
> inserted into the original XSL What we thought of was storing
> all column
> headers as XSL variables in the first transform and at
> request time pass an
> XSL param to the transformer with the number of columns and
> their order
> (probably a comma separated string) and to somehow use this
> to layout our
> columns.
> Is this the way to go?
> Does anyone have any ideas on how to implement this, or
> better yet does
> anyone have any better ideas?
>
> Thanks in advance.
>
> Lou
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp
>
>
> XSL-List info and
> archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list