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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsSkinning enhancement 1 - Classes to address all instances of a moduleSkinning enhancement 1 - Classes to address all instances of a module
Previous
 
Next
New Post
9/7/2008 6:02 PM
 

This is the first suggestion for an enhancement, provide feedback if you want.

Classes to address all instances of a module
You can skin a module through it's container, but let's say you would want to make all Survey modules background green.
There is no way to automate this ATM (unless the module supports templates).

You can address a specific module through the id of the containing div, it's something like: "dnn_ctr1248_ModuleContent"
Solution:
 IMO the core should add a modules name as a class to the div
<div class="module_announcements" id="module_id">
.....
..... Module content
.....
</div>
That way you can address all instances of a module or a specific one and it works for modules without templating too.
(or all announcements modules in rightpanes, etc.)

e.g. All modules should use this class in module.css, so Module css cannot influence anything outside the module.

Effort: Low
Risk to break existing skins: None

Gemini issue

 
New Post
9/8/2008 4:29 AM
 

Timo, this seems like a good enhancement.. :) you got my vote


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
9/8/2008 10:18 AM
 

got my vote

 

in ascx skins you can do it like

div id="mod_<%= DotNetNuke.UI.Containers.Container.GetPortalModuleBase(dnnTitle).ModuleId.ToString() %>"

 

and style with #mod_123{background-color:lime;}

 
New Post
9/8/2008 2:07 PM
 

Armand, what I mean is the name of the module as a class, so "Announcements" as a class.

Your example is for a specific module (which is already rendered like: "dnn_ctr370_DD" as an id for the module and "dnn_ctr370_ModuleContent" for it's content)

 
New Post
9/8/2008 3:29 PM
 

Timo,

If I understand this correctly then you would see the end resulting design as

<div id="dnn_ctr370_ModuleContent" class="Module_Announcement">
         <!-- Module Content Here -->
</div>

If that is the case I can't see any issue here at all, this would actually make things somewhat nice.

Now if I recall my CSS correctly this would also allow developers to nest classes two levels deep.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsSkinning enhancement 1 - Classes to address all instances of a moduleSkinning enhancement 1 - Classes to address all instances of a module


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