The difficulty with a rounded corners approach would be that it would be applied to the main level as well as each submenu level created within the default.psml file. I am seeking to only apply button images to the main menu items (HOME/FORECASTS...) and leave the submenu as text links. I attempted to find documentation on the MetaInfo <image> tag but found nothing pertaining to the syntax of it. Are there any recommendations on how best to integrate a 2 button state main menu navigation which uses the existing jetspeed menu-tab setup with minimal changes? Or at the very least has anyone accomplished something similar? Any advice or guidance you can provide is appreciated.
V/R, Kevin -----Original Message----- From: Paul Spencer [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 7:56 PM To: Jetspeed Users List Subject: Re: Menu Tab manipulation Kevin, The MetaInfo tag allows an <image> tag, although this tag is not used in the .vm files. Also their is only 1 image, not two as in your example/request. I would encourage you to use skins, including the CSS color/font/border... settings, and static images, i.e. rounded corners, to dynamically generate a tab. Otherwise you will have to develop a 2 images for each tab and language. Paul Spencer Kevin Shultz wrote: > I am trying to utilize the existing menu-tab jetspeed code but extend it to > allow for button images that operate under the same code as the text menus. > I am hoping someone out there might have a similar need or have already > accomplished this. I would like to include the ability to specify an ON and > OFF image and/or a text string for the purposes of navigation. The initial > main menu would be graphical image tabs with corresponding on and off images > while the submenu nested beneath each main menu button would be a text link > (as jetspeed is out of the box). Here is an example of the site layout I am > proposing (http://amber.metnet.navy.mil/metoc/index.jsp). My initial thought > on it would be to add fields for BUTTON ON and BUTTON OFF images under the > ADD PANE area. Whatever is entered in the currently implemented Name field > would be used as ALT tags for the button images or the actual TEXT > hyperlinks on the submenus. My experience with XML is minimal but I was > thinking something like the following for a menu entry within a users > default psml file: > > <portlets id="P-edfa4120db-1008b"> > <metainfo> > <title>HOME</title> > </metainfo> > <navinfo> > <parameter name="buttonimageon" > value="/images/nav/home_on.jpg"/> > <parameter name="buttonimageoff" > value="/images/nav/home_off.jpg"/> > </navinfo> > <skin name="metoc-gold"/> > <layout position="0" size="-1"/> > <control/> > <controller name="RowController"/> > <entry id="P-ee8aa72948-1001a" parent="FNMOC"> > <metainfo/> > <skin/> > <layout position="-1" size="-1"/> > <control/> > </entry> > </portlets> > > If the <navinfo> contains no parameters its assumed the menu entry is TEXT > only using the default $tab.Title. If there are parameters specified it > would define the SELECTED states for the main menu. If the menu entry has a > buttonimageon or buttonimageoff value then the then the jetspeed-tab.vm file > would have an if-else-end routine to account for outputting either text or > an image. As it already tracks an isSelected state "#if > ($tab.isSelected() )" then all that need be done is to display the > appropriate button state for each button. > > I realize this is all hypothetical and would love to say I could write the > code to make this happen but I have the insight of a designer and > unfortunately at this time lack the insight of a programmer. I do however > feel this would greatly enhance the overall flexibility and functionality of > an already impressive product. > > If anyone has ideas, solutions or feedback on this idea I would happily > welcome your insight and assistance. I would prefer to find a solution that > involves improving the jetspeed operation and code vice re-writing source > that would ultimately be overwritten with a future upgrades of jetspeed. > Thank you in advance for your assistance and sorry if this seems like a long > and drawn out email. I only wanted to be certain my goal was understood. > > V/R, > > Kevin > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
