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, ...Which menu?Which menu?
Previous
 
Next
New Post
6/22/2009 11:59 AM
 

Hi,

I saw that there are many skins that use TAG solpartmenu and other the TAG NAV.  Why? There are differences? What is the best?

Thanks

 
New Post
6/22/2009 4:56 PM
 

The official statement is that Solpart is deprecated and should no longer be used as it is no longer supported and eventually will be phased out altogether.  The DNN Nav menu is the currently supported menu that should be used.  However, the DNN Nav menu isn't actually finished yet... it works fine, but it lost some functionality and has several issues that limit how it is styled.  The DNN Nav menu is basically a stripped and reworked version of the Solpart code which did not carry-over all the functions available in Solpart.

Currently, the DNN Nav menu when used in DNN 5 with DNN 5 specific menu settings can do a few things Solpart can't, and there are plans for further improvements.  Being that it is a volunteer effort by one person, it's slow progress.  Were I a programmer, I'd jump in to help implement the planned changes, fix the bugs, and have it reach it's potential of surpassing Solpart in terms of functionality and unlimited design options, but I'm not.

Also, Solpart is not W3C valid/compliant while DNN Nav is.

Choose wisely.


JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

New Post
6/23/2009 5:38 AM
 

rick katzenlieber wrote
.......

Also, Solpart is not W3C valid/compliant while DNN Nav is.

Choose wisely.

 

Ok, But the 80% of skins in snowcovered uses Solpart. Also skin just made... As ever? 

Thanks

 
New Post
6/23/2009 12:00 PM
 

Well, 80% of the population uses IE as their browser, but that doesn't necessarily mean it's the best solution or that there aren't a lot of problems with it... Also, you can still use IE 4, but that doesn't mean you should and it doesn't mean you're going to get support for it either from the manufacturer when you run into problems.... I'm just restating what the core team is stating about Solpart.  At one time, it was by far the best choice and only choice.  Those 80% of skins, some including my own, may need to have their menus converted to DNN Nav at some point in order to work or function properly.  Some designers are most likely using their own "templates" to crank out all kinds of cookie-cutter "premanufactured" skins as quickly as possible and haven't taken the time to update or follow what's happening with DNN's development to follow the core team's recommendations and forewarnings.  I try to follow and keep up, and don't do cookie-cutter designs, I try to keep things unique and spend a lot of careful time on the design which is just another way of doing things.

As far as the skin goes, there are differences in the menu's css, and alignment of the menu can be tricky say if you want it centered or right aligned (one of the "lost" functions), but otherwise there are no differences in how the rest of the skin is put together.  It's just a matter of which menu code or token or object code you are going to insert into the menu area.  To be honest, the menu is probably the hardest part of skinning.  For learning, I'd definitely play with a menu setup like the Minimal Extropy menu that works and adjust the css as necessary to make sure you are overriding the defaults in default.css from the portal directory.

Also, there are third party menu modules that sell enterprise or developer licenses, they are reportedly easier to set up, true css only menus, and can be used as skin objects which could in theory be a part of the skin's install package so it could be installed with the skin as long as the license allows for that.  You'd have to check with each developer to clarify the redistribution rights granted in the EULA's.


JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

New Post
6/23/2009 3:12 PM
 

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Which menu?Which menu?


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