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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Theming, Skinning, Master Paging User Control / DNN ModuleTheming, Skinning, Master Paging User Control / DNN Module
Previous
 
Next
New Post
1/5/2008 11:59 PM
 

I've been trying for weeks to figure out how to achieve this.

Scenario:
I have a custom DNN module I've created.  It retrieves/displays information from a database (it's MLS data for Real Estate Agents).  The data is always the same, there are only so many fields in the db and they will all be displayed.

However, I have many sites all pulling from this same data.  And, guess what, I want to display in a fashion that 'fits' in their look at and feel (skin, theme, etc, for DNN that would be skin).

What is the best approach to display my .ascx files at runtime in a different look/feel based on the portal the browser (person browsing, not browser specific) is on at the time?

The bottom line, I've created a bunch of .ascx files in my module that are turned on/off depending on what the user is doing (entering search criteria, view results from that search, drilling down to the details of the results).  I have all this working great but the different criteria/results/details display .ascx's all have to come from the /DesktopModules/'MyModule' directory.  I need to to import the different .ascx's or morph/alter these programmatically (at the time of use) in a way that fits the unlimited skins that might be custom designed for any individual client of mine.

Thank you.

Barrett

 
New Post
1/6/2008 12:17 AM
 

You have a couple of options for scenarios like this, I'm not sure what the best solution, but you could do any of the following.

1. Wrap everything in divs and have defined classes for each type, alter the style for each of these classes in the skin.css file for your skin, allowing you to "override" the default layout.

2. Templatize everything, have your module read from a template, which could be a hardcoded html file, a module setting storing HTML, or any number of other ways. Have the module read the template and inject your content into the template through tokens. (see the repository module for an example of this)

I'm sure there are any number of other ways to do this.

 


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
1/6/2008 9:04 PM
 

Thank you Chris, I'll look at how the repository does this and see how it goes from there.

Barrett

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Theming, Skinning, Master Paging User Control / DNN ModuleTheming, Skinning, Master Paging User Control / DNN 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