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, ...Why .Normal and the core CSS classes must go...Why .Normal and the core CSS classes must go...
Previous
 
Next
New Post
3/29/2010 4:28 PM
 

So this one is really just to get other skinner's opinions on the core DNN classes... My vote is to get rid of the ugly critters sooner rather than later - they're an absolute headache!

Think of this scenario:

A client of ours insiste that we style all our text using em's. No problem... Well, not in straight HTML, anyway... DNN, however, is a totally different kettle of hamburgers.

For those of you who don't know, an em ("M') is a relative unit of measurement. By relative, we mean relative to the M height of a font set. And then a specified size is in turn relative to the containing wrapper's em value. So, for example, if you set the body's base size to 0.625 (or 62.5%) you end up with a base size of 10px. Read more about this here. Then if you want all your P's base size to be 14px, you simply say font-size: 1.4em; etc, etc... Simple when you know how...

But the .Normal class, for example, is EVERYWHERE... And .Normal has a default size, and is injected everywhere by DNN's core - on Divs, on P's, etc, etc. Also, .Head is injected as a default class on all container titles... This presents a problem.

Consider styling an H2 container title, wrapped in a div with the class .container-title-wrapper...

.container-title-wrapper {
font-size: 20em;
}

easy... But DNN adds a to the text (which is fine) but with the class of .Head..! And as head is commonly used throughout as a core style, it needs a base size. If it has a base size of 1.6em, then the following is the markup...

<div class="container-title-wrapper"><h1><span class="head" id="dnn_ctr???_dnnTITLE_lblTitle">The Title of this container</span></h1></div>

But .Head is already set to 1.6em in skin.css (as it's a default style). So 20em (for the H1) X 1.6 = 26em for the title... Ridiculous... You have to unwrite everything!

Also, what about .CommandButton and .SkinObject - why not just leave them as straight tags...?I know Cuong Dang has commented on this before on DNNGallery.net, and I know that Timo has created the UnloadCSS skinobject, but I feel there's no point in unloading a stylesheet when the class is still injected (e.g. Normal and Head) and needs to be supported. This is something that really needs to be addressed...

Some might say, "What about legacy installations of DNN..?" Well... It's about time for an upgrade... Older sites can stay as they are...

Your thoughts, comments, suggestions...


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
New Post
3/29/2010 8:43 PM
 

You could also try this extension on codeplex:  http://dnnskinextensions.codeplex.com...

I'm not endorsing it - I've never used it.  However, it fills a gaping hole in the community - the ability to adhere to strict style standards.

 
New Post
3/29/2010 8:57 PM
 
dmeiser, this has already been mentioned before as imperfect solution. I agree, there should be a host setting to turn off loading of default.css, which would leverage much of the pain IMHO.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/30/2010 3:39 AM
 

I agree that it would be nice to not have to work around the default CSS. Atfer a while you get used to it and there's always ways to work around the settings by targeting the css, so for example with the .Head being injected around all titles I just override this with the following h1 .Head selector.

I can see the advantage of already bringing style into DNN through the default.css so things look okay to start with, but it would be great if this only kicked in when the default skin was applied. This way, skin designers can have complete control over every element without fighting with existing styles.

Rick.



PSDtoDNN - You supply the artwork... we'll build the skins!™
Website | Twitter | YouTube | Skype
 
New Post
3/30/2010 6:34 AM
 
Rick Beddie wrote:

so for example with the .Head being injected around all titles I just override this with the following h1 .Head selector.

Rick, thanks. I did kind of make references to a solution and I know perfectly well how to fix it.

Also, to those who aren't following along properly (dmeiser), please see my comment, "and I know that Timo has created the UnloadCSS skinobject" - Thank you Sebastian for pointing out my note on it not being perfect. Glad to see someone is paying attention...

My point is that you shouldn't have to unwrite anything... And we shouldn't have to get used to working around these issues. UI's and technology should be conforming to us, not the other way around.


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Why .Normal and the core CSS classes must go...Why .Normal and the core CSS classes must go...


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