Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...dnnMENU question for the Skinning TeamdnnMENU question for the Skinning Team
Previous
 
Next
New Post
6/17/2008 11:12 AM
 

Jon Henning wrote

Been a long time since I have looked at this.  Salar is correct on one thing, those properties are carry over from Solpart's implementation.  Jan is also right, in that the document was not updated to reflect what actually got implemented.  That said, if you look at the code, you will see that if those properties were implemented all that would happen would be the SeperatorHTML (left/right) included would simply get wrapped in a SPAN tag with a class defined.  I'm guessing the reason I commented out the menus ability to do this is someone suggested this was not needed as we are already specifying HTML, which could be its own tag. 

So to get the ability to specify class tags for the seperators it should be as simple as specifying your classes in your seperators.  Instead of

SeparatorLeftHTML="LEFT" CSSLeftSeparator="myleftseparator"

You code this

SeparatorLeftHTML="LEFT"

This gives you complete control over how it gets rendered (you aren't stuck with SPAN tags).

 

Wow,

Thanks to Jon Henning that everything is finally cleared. I haven't tested all the attributes provided in the document, however, several of them seem to be working great. I'll spend sometimes on it and report any issues arise.

I have (as many others that I know) spent tremendous amount of time to get around this, but there was no luck.
Thanks again Jon.

 


Cuong Dang
Co-founder: Enliven, dnnGallery
LinkedIn | Twitter
I'm the author of DNN and Web Standards Wrox Blox

 
New Post
6/17/2008 11:15 AM
 

Brandon Haynes wrote

Hi Cuong,

I agree -- short of some dnnMenu guru showing up in this thread, my next step would be making debugging modifications to the provider and deploying it to a dev DNN bin directory.  A couple well-placed Response.Write's will probably yield more information than a dozen forum posts. 

Let me know if you need any assistance in getting a debugging setup started (though it sounds like you already have a pretty good handle on it).

Brandon

Brandon,

It's very kind of you to offer some help. I appreciate it.
Jon has helped us to get this clear.

Thanks everyone for your input here.

Have a good week!


Cuong Dang
Co-founder: Enliven, dnnGallery
LinkedIn | Twitter
I'm the author of DNN and Web Standards Wrox Blox

 
New Post
11/25/2008 2:54 PM
 

Jon Henning wrote
 

Been a long time since I have looked at this.  Salar is correct on one thing, those properties are carry over from Solpart's implementation.  Jan is also right, in that the document was not updated to reflect what actually got implemented.  That said, if you look at the code, you will see that if those properties were implemented all that would happen would be the SeperatorHTML (left/right) included would simply get wrapped in a SPAN tag with a class defined.  I'm guessing the reason I commented out the menus ability to do this is someone suggested this was not needed as we are already specifying HTML, which could be its own tag. 

So to get the ability to specify class tags for the seperators it should be as simple as specifying your classes in your seperators.  Instead of

SeparatorLeftHTML="LEFT" CSSLeftSeparator="myleftseparator"

You code this

SeparatorLeftHTML="LEFT"

This gives you complete control over how it gets rendered (you aren't stuck with SPAN tags).

I tested this
SeparatorHTML="<span class=myseparator><img src=&quot;separator.gif&quot;></span>"

 
But it does not work.

 
New Post
11/28/2008 11:58 PM
 

No, it doesn't, not worth a toss really.

If you're looking to make hover tabs, with variable widths, you can do what I ended up doing after trying to get both the NAV and SOLPARTMENU to play nice (which they wouldn't).

Instead of using the selected states and all that rot, just do this:

        CSSNodeSelectedRoot="main_dnnmenu_rootitem_selected"
        NodeLeftHTMLRoot="<span class='menuLeft'>&nbsp;</span>"
        NodeRightHTMLRoot="<span class='menuRight'>&nbsp;</span>"

Now in your css:

.main_dnnmenu_rootitem_selected span.menuLeft  {}
.main_dnnmenu_rootitem_selected span.menuRight {}

You'll have to tweak your padding and widths, but I think you get the idea :)

 
New Post
2/11/2009 9:01 AM
 

Sorry to dig up an old call but im thinking the solution above may solve my problem and as I am new to all this I need someone to clarify somthing for me

I have a skin with a horizontal nav bar with a button effect background and I need to space the menu items to fit in he buttons, as each menu item is a different size I need to find a way to space each one differently, and im hoping th above code will do the trick?

What I would like to know is will this code help me for what I would like to acheive? if so, does the first set of code go in the xml file?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...dnnMENU question for the Skinning TeamdnnMENU question for the Skinning Team


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out