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 to make proper skinsHow to make proper skins
Previous
 
Next
New Post
11/12/2010 11:57 PM
 
I had to train a designer in creation of dnn compliant skins, using the html method. Not so complicated, once you get the hang of it. The only problems are css-related, and these are the same for the html method as for the ascx method.

But there is one thing bothering me: when I compile the skin to ascx format using the dnn Skins module, the module keeps telling me that my skin is a legacy skin.

Am I overlooking something or would that be a little buggy gone unnoticed?

____________________________________
The one-eyed in the land of the blind.
 
New Post
11/13/2010 12:03 AM
 
I just tried out the Minimal Entropy skin in the Skins module. That seems to be a legacy skin too.

____________________________________
The one-eyed in the land of the blind.
 
New Post
11/13/2010 12:43 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក) wrote:
Minimal Entropy.

 read: Minimal Extropy Sorry!


____________________________________
The one-eyed in the land of the blind.
 
New Post
11/13/2010 4:24 AM
 
Marc, "legacy" means DNN 2-4 packaging format, it is not connected to skinning techniques used. since Minimal Extasy was created to be used in DNN 4.9.0 as well, it needed to be packaged in legacy format (simply zipped up instead of using a manifest).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/14/2010 8:43 AM
 
I have never packaged a skin. Packaging is only necessary/useful if you cannot access the skin folders directly. I create my skins om my computer on a local computer and then copy the whole thing to the host computer. In the beginning, I had also the startern kit installed, but I discovered I didn't really need that to create skins.

The packaging only matters when you install a new skin, now as an extension. When you install a legacy skin, you will get a warning and be asked to confirm that you are installing indeed a skin. Whatever method you use, your skin will end up in one of the Skins or Containers folders.

The next part is what I don't understand. The Skinning module will find the skinning files in the folders where the extension module has planted them. At that moment, the presence or absence of a manifest should no longer be important for the compilation of a html file to ascx format.

Forgive me my ignorance. For me, it would seem logical that the term "legacy" in the skinning module would refer to the usage of objects instead of object tokens in the html file. I cannot see the logic of warning that the skinning files have been placed in their apropriate folders without a manifest file before (or after) the translation to ascx format.

And it got me mighty frustrated because it seemed I was not able to build my skins correctly :-(

____________________________________
The one-eyed in the land of the blind.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to make proper skinsHow to make proper skins


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