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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Discussion on Default.cssDiscussion on Default.css
Previous
 
Next
New Post
11/22/2006 6:46 AM
 
Hi

I'm not always happy with the css in default.css
Some skinning tasks either get really complicated because you inherit a lot of css you don't want.
(and the different ways FF and IE deal with this)

Now there are two solutions:
1. Copy all the rules you don't want to skin.css and overwrite them.
The disadvantage is that you sometimes want something not to be defined instead of defined differently.

2. Edit default.css
This makes the skin a lot less portable.

I think a better solution would be:
If there is a default.css file in the skin folder load that instead of the normal default.css

This solves another (minor) problem too:
Sometimes you don't want the user to be able to destroy the skin by editing the default.css file
Sorry then you would have to do this for portal.css too.

Anybody any comment on this idea?

 
New Post
11/22/2006 8:16 AM
 
AFAIK, default.css shall declare default settings, in order the portal owner does not rely on the skinner to have defined every class. The skinner has the option to override setting, if additional styles are needed by the portal, they can be added to default.css without breaking any skin.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/22/2006 8:34 AM
 
Hi Sebastian
I know what you mean, but my problem is that sometimes you don't want to overwride a setting, you just don't want it declared...
Have a look at all the UL and LI definitions in default.css, for every site I have to overwrite them, while sometimes I want the parent to determine what kind of list-style-type to use. Also: try using only one font on the site, then you will have to overwrite really a lot..... (if you don't edit default.css)
I also noticed that a lot of Skinnig questions in the forum are related to inherited values from default.css.

One could also argue that default.css is maybe a little to explicit, it defines the same font-family 30 times..
My suggestion would leave the standard default.css (as backup) alone and give skinners easier control I think.
 
New Post
11/22/2006 8:40 AM
 

I think it works good as it is. I usally copy all from default to my skin css.

However should I like an other wat to get the styles rendred in FTB tis now from portal.css. I would like to have the styles from my skin rendred. Some skin maker change ex normal to myskinnormal and then you dont have that in the editor.

By the way AFAIK what is that ?

Jan

 

 
New Post
11/22/2006 6:24 PM
 
Okay I seem to be the only person who doesn't like the inherited css from default.css.
Olsmar:
I guess if your creating a skin where the font-family should be "verdana", you copy the default.css style rules to skin.css and replace all Font-styles with: "verdana, sans serif"...
That's over 40 replacements......

Personally I don't like that, CSS is supposed to make life easier....
One of the advantages of CSS should be: Change the font in one place and the whole site.....

Or is there anybody that has another solution for this
(if you agree it's a problem in the first place)?

   
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Discussion on Default.cssDiscussion on Default.css


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