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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPITweak tab.IsVisible ?Tweak tab.IsVisible ?
Previous
 
Next
New Post
12/2/2006 9:36 AM
 

Sorry if I sound like a dog with a bone, but in looking at some of the code in the Solpat SDK from Jon Henning's site ( this url http://www.solpart.com/Default.aspx?tabid=77&pid=2 ) in the DotNetNuke.Menu folder in the file named   DNNTabsDataProvider.vb I found this seting.    tab.IsVisible = True  

I believe it is responsible for retrieving "visible" pages and ignoring "hidden" pages.

My question is this, if I "cloned" this skin object for the DNN menu and changed tab.IsVisible = True  to  tab.IsVisible = False would the menu then display only "hidden" pages?  If my assumption is correct, then I am close to the solution I am looking for of being able to use SolPart for dispalying "visible"  pages, and DNN menu for only "hidden" pages.     

This would allow me a tremendous amount of flexibility in using two menus at the same time in similar fashion to Nina's suggestion on this post.  ( http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/108/threadid/86755/scope/posts/Default.aspx )

Last question, hopefully not too complicated an answer.  Would it be possible to "clone" the menu and reset the tab.IsVisible setting so that I didn't loose one of these great menus for other potential uses?  If not, I would be happy if I could use one for visible pages and the other for "hidden" pages. 

Thank you for your patience with my lack of programming skills.

Clay

 
New Post
12/4/2006 10:48 AM
 

The code you are looking at is actually part of the free Solpart Menu Module.  So it is not really used in a skin object manner.  You choose the dataprovider in the module designer.  It should work though.  Just wanted to clarify things a bit.

Not sure I understand your clone question.  If the menu is pulling the DNN Tab/Page collection in each module, there is no need to clone...

 

 

 


 
New Post
12/4/2006 11:24 AM
 

Thank you for the clarification Jon.  What I am trying to accomplish is to use to menus on the same page, one pulling all tabs in the "normal" fashion, the other pulling only the "hidden" tabs and their children, both using the skin.css for styling so I don't create more css work for myself.

The only reason to "clone" one object or the other would be so that I wouldn't "loose" the normal functions of one of the menu objects.  In essence I would end up with one SolPart operating normally, and one operating with "hidden" tabs.  Alternitively I could do the same with the DnnMenu.

If there is a way to make the module use the skin.css then it opens other design doors for me and I might be able to go that route.

Keeping it all simple though is this.  If I could use the menu skin objects so that one (Solpart) pulled tabs normally and one DnnMenu) pulled only "hidden" tabs then I would have what I am looking for as both would use the skin.css for styling.

Thank you for your input Jon,

Clay

 
New Post
12/6/2006 10:14 AM
 

While it is possible to place the css for the menu module in the skin.css file, I don't think this is what you are after, as you will have unique class names for every instance of the module.  All you would accomplish is consolidate your css into a single file.

You question about the IsVisible as far as the core goes, is a little complicated, due to its support of POD.  I won't go into details, but it would require a core mod to get that to work.  Not saying it is not a good idea, just not going to happen soon IMO.

Having said all this, I think your best option will require a little programming. I suggest taking the source from the menu module and tweaking it a bit to allow its menu to use the same css classes as your skin.  As I mentioned earlier you would also make a new data source provider to allow for your IsVisible logic to work.


 
New Post
12/6/2006 6:05 PM
 

Thank you so much for the input Jon.  Your last suggestion about tweaking the module to use the skin.css and creating a new dataprovider is probably the best one I have had. 

I'll look around in it a bit and if I have any further questions I'll get back to you, but I think this should do it.

Clay

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPITweak tab.IsVisible ?Tweak tab.IsVisible ?


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