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, ...Skinning methodology and approach.Skinning methodology and approach.
Previous
 
Next
New Post
3/22/2007 1:18 AM
 

Hi

I'm new to this forum , and new to skinning.  I've downloaded, read and digested the dnn skinning guide, and have produced my first set of basic skins.  The second set will be slicker, for sure.

In producing these skins, I have asked myself a lot of questions, which I'm not sure of the answers.  I'm sure they've been asked before, if they have been answered already, please direct me to the appropriate resources.

These questions apply to dotnetnuke 4.4.1

  1. What do I do with default dnn styles?
    DNN generated pages refer to 4 specific css files.

    /SEHR_DNN/Portals/_default/default.css
    /SEHR_DNN/Portals/0/Skins/skin_hcnt/skin.css
    /SEHR_DNN/Portals/0/Containers/container_hcnt/container.css
    /SEHR_DNN/Portals/0/portal.css

    I know my skin is contained in skin.css and container.css
    My concern is with default.css.  This has a lot of styles already pre-defined.
    Some of these are playing havoc with my layouts - others are using conventions inconsistent with accessibility conventions (eg font-size:11px).

    In my skins, I've found it necessary to completely override all of the styles found in default.css. 
    Is there a better way to do it?  Can I delete all skins in default.css and start again?  (I assume no, because default projects will be broken if this is the case).  What is a sensible approach?
    I would really prefer to start with a blank ascx(or html) file, and build the skins up from scratch with no predefined css formats to override.
     
  2. Is there an accepted approach for collaboration between developers and skinners?
    For instance, it seems necessary for developers to remove layout attributes (especially height and width) - and to assign a css class name. 
    Is there a set of guidelines, or even better, a methodology for developers?

    - Another troublesome attribute is the border size for gridviews, which always defaults to 1 - and must be manually overridden by developers.
     
  3. Gridview mouse hover effect
    For gridviews, I want a :hover effect to highlight the row if a mouse is moved over it.
    This should be a simple css definition:

    .cssGridView tr:hover {
     background-color:#FFFFCC;
    }

    The problem is, it does not work in dnn generated pages displayed in IE7.
    It works in Firefox.   IE7 is documented to support it, and simple (non dnn) proof of concept pages work in IE7.

    I assume something in dnn styles (some of which are dynamically generated by javascript) are overriding this setting, but after much searching, cannot find it.


This is a long post, and I'm sure these issues have already been discussed. 
Many thanks for any help, either direct, or by pointing me in the correct direction.

Ian

 
New Post
3/26/2007 6:21 PM
 
Hi Ian

1. Default.css is ehh.. not nice. I have asked for an enhancement to be able to not load it.
Until then you can
A. Edit default.css, but it will be over written with an upgrade.
B. Overwrite all values in your skin.css

2. AFAIK there is no real standard, that's why I'm writing a text on how a developer can improve the skinability of a module. The text is not completely ready yet, but if you are interested I can send it to you (need some feedback)

3. This problem has to so with the default DTD of DNN.
If you try this in a HTML file with
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

In IE6 it will not work anyway, unless you use a script to correct this (see this website)

For IE7 you could also change the DTD to strict or XHTML although most modules will not validate.
I use a script to support the hover on non A tags (in CSS menus) in IE 6&7 as long as the DNN modules are not XHTML compliant

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Skinning methodology and approach.Skinning methodology and approach.


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