[Xweb-developers] Re: Stylesheet for 3-layer-Navigation?

[Hendrik L. <hen...@gm...>]

Tuesday, February 3, 2004, 9:40:37 AM, you wrote:

> I am just about to fly back to AUS, so you have to wait for a more
> detailed answer. Some thoughts:
> - you would need extra parameters and/or CSS styles to handle subsectio=
ns

Done that. They are called td.navNormalSubEntry / td.navActiveSubEntry

> - the XSLT has to be checked how it handles the sections and entries.=20
> You would need either a mode once you are in a section to distinguish=20
> from the standard <section> match, or you could try to match=20
> "section/section" with a higher priority than "section" itself. I would=
=20
> have to test that myself.

I have added 2 additional modes:
- insertEntryButton
  This is used to render the second layer of navigation (normally only
  entries, now also sections)
- insertEntrySubButton
  Used to render the third layer of navigation (only entries)
I have added new template matches for 'section', mode=3DinsertEntryButton=
, to
render the sections in the second layer like entries, and one for
'entries', mode=3DinsertEntrySubButton, to render the third layer.
Additionally, the third layer is rendered for the left navigation bar (an=
d
only there).

There is much copy&paste involved, and it only works in the left navigati=
on
bar, using non-nested navigation. But at least it works :)
I will try to shorten the XSLT sheet a little bit, and make it easier to
understand.

Maybe its better to create multiple versions of the stylesheets - one for
each navigation type. Maybe thats easier to understand (and to change).

hli
--=20
M=F8=F8se trained to mix concrete and                                 Hen=
drik Lipka
sign complicated insurance forms                           hendrik.lipka@=
gmx.de
                                                            www.hendrikli=
pka.de