> * You really need to create a 100% custom replacement for xslMenu.incl. > Doing this is *not* a lot of work (fell free to copy the stock > xslMenu.incl and heavily modify it). Doing this is clean, reliable and > easy to maintain. Easier to maintain than attempting to heavily > parameterize the stock xslMenu.incl. Pavel ?kop?k did that successfully > in the past and it worked fine for him (thanks Pavel for your feedback!). > > OK, that's clear. We do not expect to have any difficulties modifying the stock xslMenu.incl (we already do this anyway), we were just wondering if this was the best way. Your answer says clearly that it is, so let's go for it !
Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: philippe_nobili.vcf Type: text/x-vcard Size: 329 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20090416/d684fb49/attachment-0001.bin
