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, ...How would you?  If not, it would be cool!How would you? If not, it would be cool!
Previous
 
Next
New Post
2/4/2007 4:50 PM
 
I like your ideas and I agree it would be great to have some configurable way to have more skin variations without having to copy the same ascx file all the time.
I had the idea before that it would be great to have some possibility to create a css variant of a skin.
My idea was to create subfolders in the skinfolder with extra css files like this:

skinfolder content:
    myskin.ascx
    myskin.css
    myskin (folder)
             version_blue.css
             version_red.css
This would create the following skin choices:
    myskin
    myskin version_blue
    myskin version_red


I think you idea (if I understand correctly) of the possibility to select multiple extra css files opens up loads of extra skinning possibilities and avoids a lot of duplicate coding.
Last month I created a skin where all the root pages and their descendants had to have a different border-color.
In principle this means copying 13 ascx files with the same content and changing them all if something in the skin has to be changed. (By the way I mostly try to solve this a much as possible by using includes)

"Of course, this brings up another point I would love to see in DNN someday and that is role/user based settings an virtually every option in DNN."
Your right, that would be great. I guess it's a lot of work, but it would make DNN even more powerfull.
What I wrote before about not trusting customers is not correct, I mean the content managers that work for the customer. Some of them are just impossible, even if they have been instructed what to do and what not they still use every possibility to avoid the companies standard. (example: selecting another font in the HTML editor / type everything in capitals etc).
And there more precise user right settings would be very helpfull.
 
New Post
2/4/2007 5:18 PM
 

I agree about the rights and permissions, it would probably be a lot of work and require some form of defaulting to allow older modules to compatible, but it sure would be nice from a corporate point of view where they want strict control on just what different people or roles can reach.

The skinning configuration manager I think would not be too hard of thing to build though: 

  • There would have to be a new button added to the skin selection menu to bring up the configuration (and maybe only appear on the screen if they selected skin has a configuration xml file or just be disabled if not available).
  • The configuration manager would then read the xml file building a tabs from the groups and build out the components on the tabs.
  • Then there would have to be an updater that cycled through the different types (in the example there were only three types but they sure would cover most needs from just them) and update the CSS overriders as needed.
  • The killer one would be to dig in DNN as to where the css includes for the skin is all generated (there is one extra I know that may need updating and that is in the free textbox provider).

Most of it sounds fairly easy but the last step.  May have to look more into it.  Sure would be nice to have this functionalty, I know it would save me a lot of time on different versions of skins in skin packs!

 
New Post
2/4/2007 6:26 PM
 
"The killer one would be to dig in DNN as to where the css includes for the skin is all generated (there is one extra I know that may need updating and that is in the free textbox provider). "
What do you
mean exactly ?

Did you add your ideas to Gemini?

 
New Post
2/4/2007 8:58 PM
 
Nope, have not done that before.  Probably shortly.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How would you?  If not, it would be cool!How would you? If not, it would be cool!


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