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, ...need desperate help learning dnn skinningneed desperate help learning dnn skinning
Previous
 
Next
New Post
5/30/2011 6:00 AM
 
Re: what's in the links; I'm honestly not entirely sure, as the template I was given to create the skin from is based off of the Romanian version of the website... *headdesk* Judging by the current website, some of the links will go to internal pages, others to external pages. A majorly un helpful thing here is that I do not have access to the current website or anything.

Stupid question: Where would I put the javascript? In the HTML files? I just want to make sure that they won't get stripped out when it's converted, or anything silly like that.

For the localization, the problem is that the design has both language links always available - one is on one side of the page and the other is on the other side. How can I make both links always appear, and appear differently depending on which language is selected? I can simplify or even excise the given mechanic if I need to, but I'm trying to change as little as possible since I'm already futzing with the design everywhere...

That said, I'm going to go look at the menu stuff you guys mentioned. I've gotten most of the design at least working so far, so the main nav menu is the biggest thing I'm still missing at this point.

Thank you for your help, guys.
 
New Post
5/30/2011 6:31 AM
 
Re the links - 

This could be done with the HTML module and some jquery or javascript.
As to where the code would go ... that depends on a number of things.

By default the HTML RAD editor clear any script code u may enter.
There are ways to change this setting however - especially if you switch to the dnnwerk rad editor provider http://radeditor.codeplex.com/
If you go down this path you can place javascript or jquery in any HTML module - of the two jquery would be my preferred option.

What I am concerned about however is that you may not have a full understanding of how DNN works.

The SKIN you are working is actually only a FRAMEWORK for your site - NOT THE ACTUAL CONTENT.

Your skin will define the layout and style and looks for your site - its is then DNN that will actually manage the display of content.

As such - you would not actually create a HTML file for something like a LINK list - instead you would at run time - add a HTML module to the page where u want the list displayed and insert you html code into that module.

This would be unless this LINK list was to be displayed on all pages in your site as part of the skin for example - in while case you could look at other options.

Also understand that with DNN the menu is generated dynamically at runtime by the system based on information stored in the database.
So when you are creating the "MENU" again what you will actually be doing is creating a layout and template that DNN with populate with actual menu items and links etc.

You could do the FLAG buttons with some asp.net code within the skin ascx file that dnn with generate the final import.

Westa
 
New Post
5/30/2011 6:55 AM
 
Well, first off I won't deny one bit that I'm totally flying by the seat of my pants here. Like I said in the first place, I was entirely unqualified for this job and the only reason I got it is because... I'm really not sure. I shouldn't have gotten this job, I might never touch DNN again in my life, and besides I've gotten the impression that this wouldn't be an easy skin to implement regardless.

But in terms of what you said, this is all stuff I understand, or at least think I understand. I'm not trying to create a link list, I'm anticipating that my client will have a link list that should go inside this container, and that the link list should have some fancy schmancy bracket hover effect. So if I'm going to use javascript for example, how would I get it to not be stripped from the code (preferably *without* requiring me to learn a new program at 4am the day I'm supposed to have this done), and how would I ensure that the code ran on the generated code? What I intend to do is try and call the function on document.getElementsByTagName('a'), btw.

The menu stuff too I know - I'm mostly just worried because it does seem to require knowledge of where things are in the database. What I mean is, for example, if I were to use the built-in menu, I'm not sure what level to point to - I could always assume that it's root for example, but is that the right assumption?

There's just not a lot of documentation I've been able to find on skin objects and container objects especially, or least not in the tutorials I've been able to access. Right now I'm also trying to deal with an issue where the login module is overflowing its container and we think it's probably because I left out some container object that should be in there...
 
New Post
5/30/2011 8:28 AM
 
Bit confused about what you are trying to achieve in a container ? Containers as a rule are not places were you place code - they are basically a SKIN element that controls the appearance of the wrapper that boarders any given module configured on any page.

The structure is this:

default.aspx - BASE PAGE 
Skin - ascx 
Content Pane - placeholder points defined on the skin 
Container.ascx - when the user adds a module to a page - it is wrapped in the container - it does not interact with the Module layer its just a wrapper
Module - this is where all the real work is done.

The Skin, ContentPane and Container are all there for LAYOUT only - not content as a rule.

Anything such as a Link List or HTML or a Forum or a BLOG is rendered inside the Container by a module.
 - these MODULES are where all CONTENT type stuff should be rendered - and as such if you are trying to create a list of links with some fancy brackets this is where that would happen.  Its not really something I would do in a skin.

Also - given that I would assume such a list of links would be something that changes over time - by end users - something like this would normally be managed by a dedicated link module of some description - and it would be in this module that the fancy code would be setup etc.

Regarding the menu - there is really no need to have any knowledge of the layout of the database when creating a skin.
DNN's menu is ultimately a tree.  Each site starts with a HOME page - and may have any number or sibling pages or tabs as well as any number of child tabs etc  

So as a rule - the main menu on the skin does nothing more than point at the root.  It takes the root and renders out the menu tree defined in the database based on the template and skin structure.  What you are doing when you define the menu in the skin has nothing to do with the content of the menu or the tabs - what you are defining is the Appearance of the menu - what its colors are, how tabs, menu items, selected items etc are to rendered = DNN takes care of the hard work at runtime of ensuring that the actual menu tabs items and sub menus are there and pointing to the right places etc.

Westa
 
New Post
5/30/2011 8:44 AM
 
I have been using the video tutorials from http://www.dnncreative.com/ - they teach you every facet of how to create a skin and deploy it. Really helpful but you will have to pay for a subscription to gain access to the good stuff!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...need desperate help learning dnn skinningneed desperate help learning dnn skinning


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