Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - Re: Select Nodes from Selected Nodes [Thread Next] Re: Select Nodes from Selected NodesTo: NULL Date: 1/7/2005 9:01:00 AM Thanx! I'll check out the example next week. Yes, the condition code is quite complex... not something to be done in = XSLT. It will have to be script. --=20 Greg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com "rdcpro" <rdcpro@c...> wrote in message = news:A58A0043-0957-405E-B4F5-71BACF4205D8@m...... You probably don't even need the script section in the XSLT to do the=20 processing, unless you're trying to do something not easily done in=20 XSLT--like regular expressions, or date calculations, etc. =20 I just heard from a client of mine, and he wants my updated application = (the=20 one I mentioned), so I'll probably be finding time to work out a better=20 example of dynamic filtering and sorting, but you can take a look at = this one=20 in the meantime: http://rdcpro.com/Members/rdcpro/snippets/filterandsort/ This isn't the best way, if the document is large, but it will give you = an=20 idea. =20 I've got some improvements on it, and if you send me an email, I'll send = some more stuff for you to look at, in particular another XSLT that = filters a=20 large document (a couple thousand rows, about 2MB) using wildcard = searches,=20 and other stuff. When I get the final version with the dynamic search=20 parameter parser finished, I'll post an update to my web site example. Regards, Mike Sharp rdcpro@h... "Greg Collins [InfoPath MVP]" wrote: > I'd be interested in seeing an example. The one issue I have (which I = think can also be done with an XSLT file) is that before I process items = 1-6, I do the following: >=20 > Working with a cloned copy of the DOM, I strip out large sections I = don't want to deal with. >=20 > Then there are a whole series of items which are conditional -- the = problem is the conditons must be figured out dynamically... so grab all = of those items with conditions, test the condition in code, and remove = the item and its children if the condition fails, as these items must = not be part of the results. >=20 > Then I'm left with a much smaller subset which I process #1-6 on. >=20 > I believe I should be able to add a script section to the XSLT file to = work in as part of the processing. >=20 > What do you think? ... Sorry I have to be so vague about everything... = business work and all :) >=20 > --=20 > Greg Collins [InfoPath MVP] > Please visit: http://www.InfoPathDev.com >=20 | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
