R2i DotNetNuke® Forum

R2i wants you to have the opportunity to ask questions, post reviews, help others or just rant and rave about DotNetNuke® or any of the R2i Modules and Skins. Our team spends hour upon hour, day after day, working on custom DotNetNuke® modules and services; please feel free to ask us anything.
 
Toolbar CSS Match the DNN Menu bar?
Last Post 01 Jan 1900 05:00 AM by . 3 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Informative
mlarsenUser is Offline
New Member
New Member
Posts:49

--
06 May 2006 01:49 PM  
I realize this is not a Toolbar issue but I thought I'd see if you might have any ideas.

What I'm trying to accomplish is to match the toolbar CSS to the the same classes as the SolPart Menu bar so when skins are changed the menu bars in the application will change to match the site automaticaly.

Using the event viewer sample toolbar I assigned the table to the class=skingradient and the toolbar button normal class=MainMenu_MenuItem and the hover class=MainMenu_MenuItemSel.

The skingradient looks fine but the button normal class adds lines and the hover class causes a shift in the text.

Have you ever tried this. I'm not sure why the same CSS classes are displaying differently for the menu table/row than they would for the Toolbar menu table/row.

Do you have any thoughts on this?

Thanks
kevinmschreinerUser is Offline
Advanced Member
Advanced Member
Posts:729

--
08 May 2006 02:36 PM  
The reason you will see different results from the Toolbar and the SolPartMenu is simple, the SolPartMenu and Toolbar share completely different HTML structures, and therefore, will not render properly using CSS configured specifically for one on the other. This is solely due to the way CSS works, and that applying CSS to a link within a div will result in a different look and feel than when applied to a Link with a TD. This is based on both the way specific browsers translate (or ignore) the CSS standards, as well as the affect specific CSS format attributes have on specific types of elements.
mlarsenUser is Offline
New Member
New Member
Posts:49

--
08 May 2006 06:59 PM  
Thats too bad that would have been two simple.. Thanks for the CSS tutorial
kevinmschreinerUser is Offline
Advanced Member
Advanced Member
Posts:729

--
08 May 2006 07:53 PM  
Yeah, sorry for the confusion. Navigator was developed so that it would adhere to with a little more intelligence to the client runtime, so that it would operate faster, with less friction, more user ease, and specific emphasis on Search Engine Optimization. Unfortunatly, these are all things which cause the SolPartMenu CSS to be a poor option set for the class assignment. With that said, you CAN use the same classes, but you need to be wary of the specific attributes it uses. Especially border lines and the like. While our Navigator can (and often does) employ borders between entities, the object to which that border applied is the key.
You are not authorized to post a reply.

Active Forums 4.1
 

New York, NY • Baltimore, MD • Vienna, VA • St. Louis, MO • Seatle, WA • 410.327.0007 • info@R2Integrated.com

Bookmark & Share Bookmark and Share