xweb-developers

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

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

Hello,

the supplied generic.xsl allows only for 2-Layer-navigation (sections and
entries). Until recently, this was sufficient for my website, but now I'm
in need for a third layer.

Has anybody done this before?

I was already able to include a 'section' inside a 'section', so that it
would be displayed beside the normal entries, and it is already clickable.
But it is rendered with section colors (not entry colors) and I don't kno=
w
how to add the third layer to the navigation bar (everything is on the le=
ft
side).

Any hints?

Thanks,

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

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

[Peter B. <pe...@pe...>]

Hi Hendrik,

I don't think I ever actually did more than two layers of navigation,=20
but XWeb won't stop you. Nesting <section>s is no problem at all, the=20
only thing you have to make sure is that the stylesheet for the=20
navigation handles this. The generic one in the distribution is not=20
meant for this, although it could probably be extended towards a third=20
layer.

  Peter



Hendrik Lipka wrote:

>Hello,
>
>the supplied generic.xsl allows only for 2-Layer-navigation (sections an=
d
>entries). Until recently, this was sufficient for my website, but now I'=
m
>in need for a third layer.
>
>Has anybody done this before?
>
>I was already able to include a 'section' inside a 'section', so that it
>would be displayed beside the normal entries, and it is already clickabl=
e.
>But it is rendered with section colors (not entry colors) and I don't kn=
ow
>how to add the third layer to the navigation bar (everything is on the l=
eft
>side).
>
>Any hints?
>
>Thanks,
>
>hli
>--
>M=F8=F8se trained to mix concrete and                                 He=
ndrik Lipka
>sign complicated insurance forms                           hendrik.lipka=
@gmx.de
>                                                            www.hendrikl=
ipka.de
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>XWeb-Developers mailing list
>XWe...@li...
>https://lists.sourceforge.net/lists/listinfo/xweb-developers
>
>
> =20
>

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

[Peter B. <pe...@pe...>]

Hendrik Lipka wrote:

>Hello Peter,
> 
>Monday, February 2, 2004, 9:09:47 PM, you wrote:
>
>  
>
>>Hi Hendrik,
>>    
>>
>
>  
>
>>I don't think I ever actually did more than two layers of navigation, 
>>but XWeb won't stop you. Nesting <section>s is no problem at all, the 
>>    
>>
>
>I know, I have already done that.
>
>  
>
>>only thing you have to make sure is that the stylesheet for the 
>>navigation handles this. The generic one in the distribution is not 
>>meant for this, although it could probably be extended towards a third 
>>layer.
>>    
>>
>
>
>Exactly that was my question :) I have already displayed the section inside
>another section, but it is rendered with the wrong colors, and the third
>layer is not displayed :(
>  
>
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 subsections
- the XSLT has to be checked how it handles the sections and entries. 
You would need either a mode once you are in a section to distinguish 
from the standard <section> match, or you could try to match 
"section/section" with a higher priority than "section" itself. I would 
have to test that myself.

  Peter

[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