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, ...DNN4 skin from Photoshop, Help meDNN4 skin from Photoshop, Help me
Previous
 
Next
New Post
8/21/2006 6:13 PM
 

In all honesty, I gave up on the Slicing tool years ago, I basically just draw my design, then simply choose my images and Copy Merged, then paste and Save for Web...  I know this is the long way but in order to get my skins just right, I found that chugging out all the slices was confusing the heck outta me. But to each his / her own.

I spent a couple weeks picking apart the default skins, mainly just viewing them in Dreamweaver with the Expanded mode on in order to see how all the tables were nested. I soon realized that the designs were all very simple table-based designs with a couple tokens thrown in here and there. So now when I'm starting a new skin, I just setup a new folder with xxx_skin.html    xxx_skin.css   xxx_skin.xml   (xxx being a 3letter client abbreviation) and then just throw together a table-based layout like I used to before getting into CSS layouts (quite fun for those of us who have been beating our heads against CSS-pure sites)... I just make sure there's a [MENU], [USER], and [LOGIN] token and I can usually add the rest as I go...

Finally for the content area, I use a cookie-cutter code that I picked up here months ago (note: I also keep all my code snippets in a central folder for easy reference):

<TABLE width="100%">
  <TR>
    <TD class="toppane" colspan="3" id="TopPane" runat="server" valign="top"></TD>
  </TR>
  <TR valign="top">
    <TD class="leftpane" id="LeftPane" runat="server" valign="top"></TD>
    <TD class="contentpane" id="ContentPane" runat="server" valign="top"></TD>
    <TD class="rightpane" id="RightPane" runat="server" valign="top"></TD>
  </TR>
  <TR>
    <TD class="bottompane" colspan="3" id="BottomPane" runat="server" valign="top"></TD>
  </TR>
</TABLE>

This will give you 5 Content panes, 3 columns in the middle with a "header" and "footer" pane. Incredibally useful. One thing this lil snippet opened my eyes about is the ease of making your own content panes, simply change the class & id names and you can convert any TD element into a content pane that you can drop modules into.

I'm sure this is DNN101 for many but I like to chime in with my $0.02 every now and again.

Slainte!

SB

Edit - Quick note, once the skin is "ready" I ZIP it and upload it thru the skins interface, it will parse it into an ASCX automatically. I still cheat this way b/c I have yet to wrap my head around actual programming. Also, if you leave your XML blank, you will get a minor error when uploading the skin, however in my experience it hasn't broken anything.


Wells Doty Jr
Online Content Development
 
New Post
8/22/2006 2:56 PM
 
I like your reply, and I like tips like this. I bet some of the uber skinners have a standard template of set of actions they follow to get started.
Please share or point us/ me to these sort of a walk-thrus.
I saw a few videos (thanks Nina, and others) that were extremely helpful. But they dealt mostly with the DNN side and I seem to need help with the Photoshop/Dreamweaver/whatever-tool tool is used to turn a pretty idea into the HTML and/or ASCX code
 
New Post
8/23/2006 2:52 PM
 

I love your approach, and have to agree that slices are a pain in the butt when you need to design a full width skin and only need partial images to complete your design.

I have a separate question for everyone.   Why is Dreamweaver, for many the "standard"?  Why could I not use MS Frontpage or Expression?  Are there problems related to a DNN design with a MS WYSIWYG software solution?

Thanks.
PS:  still using Photoshop, ImageReady, and Textpad.  LOL

 
New Post
8/23/2006 4:44 PM
 

Simply, FrontPage is the debil...

More or less, FrontPage is great for those who aren't quite comfy with working with pure code and like a WYSIWYG interface like Word, however it injects ALOT... and I mean ALOT of extraneous code (lang spans come to mind in particular) which when you're building a skin (in my opinion) only serve to confuse the coder.

Dreamweaver does a nice job of giving you a design view and code/split view, but it also has an immense amount of extra tools and libraries (Javascript, HTML, etc) that can come in quite handy (not to mention, it comes with Macromedia Studio which I have for Flash & DW). I do most my work in the code view, and mainly use design to drop in tables or other elements which I'm far too lazy to code by hand. Then, once the skin is published I actually use a lil program Notepad++ to edit the CSS files directly.

I think in the end, it all comes down to taste and comfort. I started in the early 90s using DOS-EDIT and HotDog which were sparse to say the least, and it's just what I'm used to. However I still reccomend against FrontPage, but I have an admitted grudge against that program.

SB


Wells Doty Jr
Online Content Development
 
New Post
9/3/2006 2:11 AM
 

I tried out changin the skin, and i used ascx intead of the tokens but its giving me this kind of error message

An error has occurred.
Unhandled error loading module.

 

without any trace. Can anybody help wh

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN4 skin from Photoshop, Help meDNN4 skin from Photoshop, Help me


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