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, ...HouseMenu - proper syntaxHouseMenu - proper syntax
Previous
 
Next
New Post
3/19/2007 6:44 PM
 

Hi, John. Thanks so much for your suggestion. I'll take a look at the development guide tonight and will speak with my employer tomorrow about purchasing the module.

Am I understanding correctly that the page icon can be made as large as we want so that it covers the entire background of the particular menu item (ours is probably about 200 x 50 pixels) and not just a tiny image on the left or right side of the menu item "button"?

The HouseMenu I've been working so hard with pops another problem . . . the skin object installation I got is missing a code behind file--the all important "HouseMenuSkinObject.ascx.vb" file!   Waaaaaahhhhh!!!

One of my considerations is altering the SOLPARTMENU to display an additional background image just like the page icon, but that task is looking complicated.

I don't have much more time for my search. If the Snapsis menu can do the above, then it is really a lifesaver!

Thanks again for your input!  Have a great evening.

jc

 

 
New Post
3/20/2007 7:54 AM
 
Hi
If you have problems styling the "Housemenu" then "css nav menu" will not be much better, since they both render about the same; an unordered list.
I normally create my own CSS for housemenu, but with the StyleName property you can load one of the default stylesheets that come with the menu.
You could read my post in this thread about housemenu and images.

By the way, I have never noticed any difference if the Orientation was set.

The properties since the Houseofnuke site is a bit empty...
--------------------------------------------------------------
The HouseMenu properties and their possible values are as follows....

Scope (focus or root level of the menu): -1 for entire site; 0 for children of active page; n for children of tab with id n
ShowHome (whether or not to include "Home" page): True or False
ShowParent (whether or not to include parent when scope is other than -1): True or False
ShowHidden (whether or not to include hidden pages): True or False
ShowAdmin (whether or not to include "Admin" and "Host" submenus): True or False
ShowSearchResults (whether or not to include "Search Results page): True or False
SearchResultsName (name of "Search Results" page to be included): page name as string, default is "Search Results"
ShowPageIcons (whether or not to display page icons): True or False
HidePageNames (whether or not to hide page names; use in conjunction with ShowPageIcons for an all-graphics menu): True or False
IsRecursive (whether or not to include submenus for all children in scope): True or False
Orientation (how menu will be oriented on page): H for horizontal or V for vertical
Mode (how to display submenus, whether submenus will be dropdowns): S for static or D for dynamic
CssElementId (optional id to use for menu's container div tag): string value
StyleName (CSS filename for styling the menu's appearance): string value
 
New Post
3/20/2007 8:53 AM
 

JC, yes you should be able to do what you need using the Page Icons, but if not I will make sure that the menu will handle this request as I have seen it come up more than once.

 

 


DotNetNuke Modules from Snapsis.com
 
New Post
3/20/2007 10:21 AM
 

Hi, Timo. I do not have problem styling the HouseMenu--haven't a chance to run into that yet . . . I've spent almost a week doing things like tracking down the download site, downloaded both the module version & the skin object version, tried to install and use the module version but ran into some sort of object reference error in DNN when trying to use it on a tab, uninstalled it and gave the skin object version a try, spent half a day trying to find out that I needed to register the skin object in my .ascx file before I can use it (this info should have been in the Readme.txt file that was distributed with the skin object package), and then the last straw was discovering the package is lacking the all important HouseMenuSkinObject.ascx.vb file!

I don't know where to go get the file if it is not in the package. My project deadline is looming and I can't spend more time huntingdown the missing file . . . and then after that I still have to go through an earlier post of yours trying out your method of making the menu buttons graphical.

Thanks for the link to the thread on HouseMenu and images. I will take a good read . . . I definitely will play with HouseMenu more later, but right now the pressure to get the company project done is tremendous.

BTW, where can I go to get the HouseMenuSkinObject.ascx.vb file?

Thanks also for listing the properties. They have been documented in the Readme.txt file so I was using them. Anyway, I am using whichever tool that will help me complete the company project the fastest . . . and experimentation and play later.

Best,

jc

 
New Post
3/20/2007 10:33 AM
 

Hi, John. Thanks for your anticipated assistance. We will be getting the NavMenu today and I will begin to give it a try.

jc

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...HouseMenu - proper syntaxHouseMenu - proper syntax


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