Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] RandomList.xsl from FXSL-xslt2

From: Jesper Tverskov <jesper.tverskov@-----.--->
To: xsl-list@-----.------------.---
Date: 10/2/2009 4:21:00 PM
Now, in my project I have around 300 items, and I need to pair each
item with four of the other items randomly, and I will have to do that
many times a day.

I only need one seed, but I will have to make 300 transformations
every time a need to get the items "paired", so XSLT looks like not
being an option.

So far I have used C# calling a shuffle routine again and again in
other parts of the project, and I have a feeling that I will have to
continue doing it that way. Turns out to be one of the few things
being too nasty in XSLT in my particular use case.

Cheers,
Jesper

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent