|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Keys with different parents, but same name
Hi Ganesh,
At 01:27 PM 10/27/2003, you wrote: Thanks for pointing me in right direction. This indeed worked. But did not solved the problem :-(. The reason for using different keys is there could be different types of groups and styling/rendering would change accordingly. I'm not sure why that has to follow. Your earlier mail posed the problem of retrieving the correct label for a node based on its field and fieldGroup, so that's what I looked at. Keys are a useful mechanism for retrieving nodes based on pre-determined criteria (such as the values of associated nodes); how they would apply to control styling or rendering is rather an open question, in this case. Nevertheless I see no reason why the same lookup mechanism couldn't be used to handle, say, CSS styling attribute values. (Whether that would work in your case is a different question.) For brevity, i had mentioned only field and fieldGroup. May be to resolve this I think will have to look into design stuff. Most likely. :-> Since this document has already been, or must be, processed to retrieve information from it, the changing of the context node by itself does not add significant overhead. And because of the way keys work, your context node has to be in the document where you apply the key: hence the for-each. Cheers, Wendell
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








