× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Joe,
The book I'm using is your book. It's getting pretty ragged - from
use!!!
Gay

Gay Kelly* Programmer/Analyst* SunGard * GMI * 1 South Wacker Drive,
Suite 400, Chicago, Illinois 60606

Tel  1 312 577 6180 * Fax  1 866 867 4785 * www.sungard.com/GMI

CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.



-----Original Message-----
From: wdsci-l-bounces+gkelly=sungardfutures.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+gkelly=sungardfutures.com@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: Tuesday, November 01, 2005 9:54 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: RE: [WDSCI-L] Navigation on web pages


> From: GKelly@xxxxxxxxxxxxxxxxxx
> 
> Thanks Michael,
> I've used this before, and it does create great popup menus. Since
this
> is an in-house project, we don't want to spend any extra money. Do you

> know if there is any way for Web Site Designer to distinguish between 
> parent and children links or am I out of luck? Even just a slight
indent
> from the side navigation would help. Maybe this is something IBM might

> want to consider for the future if it can't be done currently?

Actually, the navigation menus are created by "snippets", which are
included as part of the template.  If you look in the generated code
from the template, you'll see the reference to the snippet; it will look
something like this:

<!-- siteedit:navbar spec="/MySite/theme/footer.html"
target="sibling"-->

When you open up the file footer.html, you will see a macro language
that you can modify to create your own navigation widgets.  There's
really no documentation except for the chapter I wrote in my WDSC book,
but if you take the time to bang through it, you can figure it out.

Here's some insight:

<!--siteedit:forEach var="item" items="${sitenav.items}"-->

This is a standard forEach loop.  Since it's working on sitenav.items, I
know that the invocation tag used the target attribute to specify a set
of web pages.

 <!--siteedit:choose-->

This statement start a standard case construct.

  <!--siteedit:when test="${item.self}"-->
               <tr>
                  <td class="nav-s-highlighted">${item.label}</td>
               </tr>
  <!--/siteedit:when-->

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.