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, ...tables VS divstables VS divs
Previous
 
Next
New Post
1/4/2008 4:26 PM
 

That's a pretty simplistic view Jeff. I'm not a web designer other than as an occasional hobby (I do maybe 4 or 5 skins in a year). I work 8 hours a day (quite often more than eight hours), spent three or four evenings with my son training, spend countless hours programming/bug fixing/etc. on the AD project, and then there's my wife, two daughters, and assorted pets to spend time with. I would love to "read up on how to do it properly" but the simple fact is that unless it's your livelihood or you have no life that's not possible. I've spent days trying to figure out how to get something to work properly using CSS/Divs/Spans/etc that I could have done in an hour using a table with a class assigned to it. And I've yet to find anywhere where you can get away with a non-fixed width display that uses graphics (not colors) just using Divs/CSS that doesn't get borked up at some point. I looked at Lance's yahoo suggestion and it would work fine as long as I didn't try to use graphics.

Going full css/xhtml requires the same skills as an experienced programmer imho. Yeah you can do a "Hello World" program in the first hour (or less) of learning how to program and you can do a simple tableless layout with little training but if you want to get into anything fancy it takes the same amount of training/time as it does to do anything fancy with a program.

Also, for those complaining about module developers using tables. A lot of the time the programmer has no say in how the control is rendered as it's done by the .NET framework. A datagrid returns a table and that's it (though it may have changed in VS2008).

 
New Post
1/4/2008 4:42 PM
 

Mike Horton wrote

That's a pretty simplistic view Jeff. I'm not a web designer other than as an occasional hobby (I do maybe 4 or 5 skins in a year). I work 8 hours a day (quite often more than eight hours), spent three or four evenings with my son training, spend countless hours programming/bug fixing/etc. on the AD project, and then there's my wife, two daughters, and assorted pets to spend time with. I would love to "read up on how to do it properly" but the simple fact is that unless it's your livelihood or you have no life that's not possible. I've spent days trying to figure out how to get something to work properly using CSS/Divs/Spans/etc that I could have done in an hour using a table with a class assigned to it. And I've yet to find anywhere where you can get away with a non-fixed width display that uses graphics (not colors) just using Divs/CSS that doesn't get borked up at some point. I looked at Lance's yahoo suggestion and it would work fine as long as I didn't try to use graphics.

Going full css/xhtml requires the same skills as an experienced programmer imho. Yeah you can do a "Hello World" program in the first hour (or less) of learning how to program and you can do a simple tableless layout with little training but if you want to get into anything fancy it takes the same amount of training/time as it does to do anything fancy with a program.

Also, for those complaining about module developers using tables. A lot of the time the programmer has no say in how the control is rendered as it's done by the .NET framework. A datagrid returns a table and that's it (though it may have changed in VS2008).

I reiterate: http://www.456bereastreet.com/archive/200704/lame_excuses_for_not_being_a_web_professional/

 
New Post
1/4/2008 5:04 PM
 

I don't see anything in there that I don't disagree with and it's what I would fully expect from a web professional however not everyone who does skins is a web professional. I'm not, at least in the design aspect of it. 

I do take exception to the line "lazy, ignorant, incompetent people" though as I'm far from any of the three.

 
New Post
1/4/2008 5:06 PM
 

Mike Horton wrote

I don't see anything in there that I don't disagree with and it's what I would fully expect from a web professional however not everyone who does skins is a web professional. I'm not, at least in the design aspect of it. 

I do take exception to the line "lazy, ignorant, incompetent people" though as I'm far from any of the three.

Well those are his words directed at people who are paid and titled as web professionals. If you don't count yourself in that group then he wasn't talking about you. My point is i'm seeing a lot of excuses in these threads like "CSS is too much work" or "CSS causes more workarounds"

It really doesn't, if you understand it better.

 
New Post
1/4/2008 7:31 PM
 

Joseph Sak wrote

 Timo Breumelhof wrote


"You should use tables for tabular data and divs for the rest"

IMO at least 95% of the skins can be done without tables.

 

 

These two statements are inaccurate. You can use standards compliant css/xhtml 100% of the time and should. Never use tables for layout structure. Ever.

Second, you shouldn't just "use divs for the rest". It's worth reading up on semantic html and learning what tags to use where

 

Hey Joseph, I was being political...

I wrote "at Least"...

Also we where talking about tables vs divs for basic layout, not menus, headings etc...

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...tables VS divstables VS divs


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