|
Sounds like you're not familiar with the original[^], to which the Simpson's blorb refers.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Yet that's their whole purpose.
I suspect your pants are so tight that not enough oxygen is getting to your brain.
modified 2-Dec-16 22:19pm.
|
|
|
|
|
Once everyone stops using IE6 (or any version of IE, for that matter), and upgrades their ancient versions of Firefox[^], maybe a proper CSS layout would make sense.
Until then, it's probably too much arse-ache for too little benefit.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
There are only 0.03% internet users that use IE6 (soure: "Can I use" usage table[^]). So I think if Code Project update there CSS whitout table tags if not needed, this percentage will be lower than 0.001%.
|
|
|
|
|
It's still going to break the site for some users, and require a lot more work to keep the site working for most of us.
What benefit do you think you'd get out of a CSS layout redesign? Are you using a screen reader which is struggling with the table-based layout?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Hein Pauwelyn wrote: There are only 0.03% internet users that use IE6
That's awesome news!
So, when are you going to donate your time to convert CodeProject's entire site over to use a proper CSS layout? All free of charge of course, because you're a great guy!
|
|
|
|
|
Richard Deeming wrote: proper CSS
That's an oxymoron!
|
|
|
|
|
What's an "oxy"? And don't call me a moron! 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
As you can see, tables can be used for layout.
SCNR
|
|
|
|
|
Hein Pauwelyn wrote: cannot be used
It can be used - as you've seen. Though tables are meant for displaying tabular data such as a grid, but that doesn't mean you cannot use it for layouting. Most folks uses tables for layout because their CSS skills aren't good or to support ancient browsers.
|
|
|
|
|
unlike css, tables-for-layouts works in html email (and inasmuch common practice).
- same source translates well to almost any browser, old or new.
- so why use something that only works some of the time when there is another way works all of the time?
anyway, in too many case css is like racing stripes on a car, while kiddies think it looks cool, in some places it's just wrong, and they don't make the car go any faster either.
Sin tack ear lol
Pressing the "Any" key may be continuate
modified 2-Dec-16 9:37am.
|
|
|
|
|
Tables were used for layout for 15 years before CSS came. Just because something is new, doesn't always mean that it is better. There's no reason to wrinkle ones nose at "old" technologies just because something "new" is available.
I still consider tables superior to CSS as far as layout is concerned. It's not because I don't know CSS, just because I don't like it!
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Yes, tables are! Unless you're only targeting mobile devices. In my organization, there are still people using IE 8 and many of the applications I developed were for IE 6 because a couple of years ago, people were still using it. I won't rewrite for the sake of it and some of my tabled applications still look good on phones.
|
|
|
|
|
|
Hein Pauwelyn wrote: Some designers knows that tables cannot be used for layout.
And the rest of them don't subscribe to idealism and get the work done using whatever works best.
|
|
|
|
|
Hein Pauwelyn wrote: Some designers knows that tables cannot be used for layout.
But those out in the real world (as opposed to an academic Ivory Tower) know they can. And are. Because they work.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It's just guidelines[^]
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Just like screws cannot be used as nail.
..but after a while, I'm not that picky anymore. Screws, nails, glue. Anything that works 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hein Pauwelyn wrote: Some designers knows that tables cannot be used for layout
Important life lesson for you here young man. Don't believe all you read.
Pragmatic designers know that adhering to dogmatic ideas just for the sake of adhering to arbitrary rules is the quick way to madness and that there are better things to waste your time on.
This space for rent
|
|
|
|
|
Like spending all your time on CodeProject 
|
|
|
|
|
Hein Pauwelyn wrote: tables cannot be used for layout
Really? So how do you layout a table of data?
What you mean is: some designers prefer you don't use tables. And this has lead to designers using everything but a table to do things that, really, should be done using a table.
For us: yes, we have tables for layout where we shouldn't. We're actually in the midst of planning updates to this. However, there are cases where tables actually provide layout safety because a table can reign in bad HTML. If you allow user generated HTML (like these forums) then you need a mechanism to ensure the HTML they provide doesn't break things. HTML and CSS filtering works (mostly) but there will always be cracks. Sandboxing (sort of) this HTML inside a table has proved (for us) to be a neat safety feature for wayward HTML.
cheers
Chris Maunder
|
|
|
|
|
I add that to the list.
* Pointers are bad, everything must be an object;
* Managing memory is bad, everything must be garbage collected;
* Native is bad, everything must be interprteted or JIT-compiled;
* Performance doesn't matter, computer power is illimited;
* Tables cannot be used for layout.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Missed one:
* Goto's are bad, everything must be wrapped in a giant if/else structure with nearly duplicate code in both branches.
|
|
|
|
|
Let me tell you a developer's secret:
It's OK to use <table>. It's easy to use - and it works.
| REALLY! |
|---|
| You Can Do It | | And Won't Burn In Hell | | You Can | | Do It! |
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
From one web developer to another, I agree. Tables should only be used for showing tabular data, not layout. However, keep in mind CP has been around a long time, way before CCS3 or even CSS2 became popular. People used to use tables for layouts before CSS2. These days it's discouraged (rightfully so), but the creator of CP (Chris Maunder) has been around since dinosaurs roamed. And you can't always just up and change a website that serves millions of people so quickly.
That being said, for any new development you're doing, definitely do not use tables for layouts... just tabular data.
Jeremy Falcon
modified 2-Dec-16 15:12pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
