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, ...Making a skin, or modding a skin?Making a skin, or modding a skin?
Previous
 
Next
New Post
12/15/2008 8:11 PM
 

Well after you upload is converted to scx anyway so why not code directly in it . You dont need to worry about xml settings and because youa re using ascx you can also directly code in it to include tabid or tabname with request.querystring to give a bit more functionality to your skin

Ahhhh..hardcode tabid's into the skins???  Ouchie!  What happens when you delete a tab and recreate it?  gots to go back into the skin again and modify it...the point of a skin, from what I understand, is to have reusability.  As for ascx vs html to skin.....Here is why I would start with html/xml.

Lets say, you create a skin, and you take your time to create all kinds of css classes for your menu system, that you like better than the ones normally defaulted....now you just save them in the XML file, and viola, use it in all your skins.  I'm pretty sure my first skin is not going to be my last :->

Try and write out all the settings for DNNMenuNavigationProvider every time you want to write a skin..having to recreate all your css classes...OR cut and paste  it in from an old ascx skin that is the "latest" incarnation of the css classes you wanted, where is that burried again...or...viola, just grab my xml file and parse it...and now I'm consistant with all my skins.

 

Personally, I would never hard code a value into a skin when the expected(hard coded value) has a chance of being changed intentionally or not....bugs start eating at your website.

 

Tables Vs Divs.  You can make it valid as you want in pure CSS and it's still gunna wierd out in IE.  Tables seem to keep things pretty neat and orderly for now.  Check out the new extropyblahblah skin, it gets all jacked up.

 

And thos are my 2 cents back :->

 

 

 


Josh Martin

 
New Post
12/31/2008 7:46 AM
 

Hi

 

You should read better, I mentioned if You use .net code you could read out tabname or tabid from querystring and do something like

 

<  img src="<#%request.querystring("tabid")%>.gif"/  >

 
New Post
1/1/2009 7:06 PM
 

IMO, it all comes down to the skin you start with, choose a clean skin and then it's ok.

If not you'll get into trouble for sure.

BTW if you know how to use Firebug, skinning is not that difficult IMO.

 
New Post
1/2/2009 10:05 AM
 

Josh Martin wrote

Personally, I would never hard code a value into a skin when the expected(hard coded value) has a chance of being changed intentionally or not....bugs start eating at your website.

I pretty much hard code the links to terms, privacy, legal, etc in my skins, using the Friendly Name URL.  Helps with SEO for one thing.

Jeff

 
New Post
1/2/2009 11:04 AM
 

If you are confident with html/css then you'd better start from scratch, as clean skins are hard to find. If you are familiar with Visual Studio, I would suggest that you use that as your workbench and go with ascx skinning. You can even start with a div/css layout you can find all over the internet. So first you setup your skin structure.

Next you copy and past the skinobjects you need from the default dnn skin (both register tags and controls). now you are pretty much set to start developping using css mainly.

A word of caution: If you are not familiar with css, you are in for a bumpy ride, but if you want to learn and have some stamina, I am sure you can do it.

Peter


Peter Schotman
Cestus Websites voor DotNetNuke oplossingen in Nederland
Contact us for your custom design and skinning work.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Making a skin, or modding a skin?Making a skin, or modding a skin?


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