Author | Message | Time |
---|---|---|
Invert | I know I have not posted here in a long while since I have been busy but I do read this forum frequently. I just wanted to make a poll to see how many people move ahead in the web development circle and how many still cling to their old ways. I have a friend that only used tables for website design, I helped convert him to use CSS. How many people here still use tables for design? How many people here used SMIL before? | February 10, 2005, 10:33 AM |
Mitosis | I mostly use tables and then style them with CSS. Haven't really done everything in CSS before. I guess I'm just comfortable with how I do it. | February 10, 2005, 6:49 PM |
po0f | Xhtml for content, css for layout and pretty stuff. | February 11, 2005, 12:52 AM |
kamakazie | [quote author=po0f link=topic=10504.msg99215#msg99215 date=1108083168] Xhtml for content, css for layout and pretty stuff. [/quote] same. I like to separate document (XHTML) from style (CSS). Makes it easier for people using a cell-phone or even the blind, not that it's my target audience. Additionally, it's easier to change layouts as you just modify a css file and you're done. | February 11, 2005, 2:43 AM |
peofeoknight | xhtml is not more accessible than html, infact the opposite is true. The reason is xhtml is still new and our browsers are not handleing it all the same way. Basically xhtml can never be more accessible then html, it can be as accessible, but never more. I am using a mix of both html and xhtml, but I think that for the time being it is probably best to use 4.01 strict. [quote author=Invert link=topic=10504.msg99156#msg99156 date=1108031585] I have a friend that only used tables for website design, I helped convert him to use CSS. How many people here still use tables for design? [/quote] Tons of people saddly. Most major websites still run tables because it is a pain to change things, but even the places that use css tend to not have valid code. www.macromedia.com and www.lycos.co.uk and www.espn.com are examples of corporate sites using css but their markup is still crap. One step at a time I guess [quote author=dxoigmn link=topic=10504.msg99220#msg99220 date=1108089782] [quote author=po0f link=topic=10504.msg99215#msg99215 date=1108083168] Xhtml for content, css for layout and pretty stuff. [/quote] same. I like to separate document (XHTML) from style (CSS). Makes it easier for people using a cell-phone or even the blind, not that it's my target audience. Additionally, it's easier to change layouts as you just modify a css file and you're done. [/quote] The advantages of css include but are not limited to: Lower bandwidth, if you use the same css file for every page of your site that code only has to be downloaded one time. better code organization, you code will be much cleaner accessibility, as you said when a browser cannot handle css the css will not be displayed (remember to use <!-- around it so that older browsers do not print out the css). I also use css and keep my structural markup separate from my presentational markup. | February 11, 2005, 6:02 PM |
Grok | I don't like, and don't adhere, to making exceptions in my code for older, non-compliant browsers, such as the <!-- -> around certain elements. If my doctype says I am XHTML 1.0, and you cannot properly parse it, then don't do it. That older browsers (and who uses IE 3.2 anyway?) are poorly written is not my problem. The user calls me I tell them on the support desk that they need to access the page from a newer browser device, and will give them options and download locations. | February 11, 2005, 6:33 PM |
peofeoknight | [quote author=Grok link=topic=10504.msg99302#msg99302 date=1108146816] I don't like, and don't adhere, to making exceptions in my code for older, non-compliant browsers, such as the <!-- -> around certain elements. If my doctype says I am XHTML 1.0, and you cannot properly parse it, then don't do it. That older browsers (and who uses IE 3.2 anyway?) are poorly written is not my problem. The user calls me I tell them on the support desk that they need to access the page from a newer browser device, and will give them options and download locations. [/quote] It is not always that simple. I should have included nongraphical browsers in the mix too with that post. There are audio braille browsers that mihgt read your code incorrectly and your search engine spiders could read it incorrectly (but them seeing some css really isn't a big deal). The idea is just going a little bit out of your way will make your website work on all platforms, no one gets excluded. | February 11, 2005, 10:46 PM |
Invert | I'm actually working on a new site right now and I am using XHTML with CSS2 I don't care if your old browser can't handle that but I am including support for none graphical browsers. I use my cell phone sometimes to go to websites to get news and it's nice to be able to do that. | February 11, 2005, 10:58 PM |
peofeoknight | [quote author=Invert link=topic=10504.msg99338#msg99338 date=1108162710] I don't care if your old browser can't handle that but I am including support for none graphical browsers [/quote] You should care about all browsers. I test sites on the following: IE6, IE5.5, IE5, IE4, GECKO (NS and MOZ), Opera, Lynx. Now I am not really concerned so much with how it looks on some of those, but I am concerned with it working. I just want to make sure that someone on any given platform can get to my content. I am not going to hack the heck out of my layout for one minor client because a few images are misaligned. | February 11, 2005, 11:28 PM |
kamakazie | [quote author=quasi-modo link=topic=10504.msg99297#msg99297 date=1108144976] xhtml is not more accessible than html, infact the opposite is true. The reason is xhtml is still new and our browsers are not handleing it all the same way. Basically xhtml can never be more accessible then html, it can be as accessible, but never more. I am using a mix of both html and xhtml, but I think that for the time being it is probably best to use 4.01 strict. [/quote] They're more accessible than most HTML 4.01 pages. When you start mixing design with data then it becomes harder for a browser to present the page to someone who is blind or someone using a cellphone. Using XHTML + CSS allows you to specify certain stylesheets for different medias (i.e. cell phones/pdas, printing, screen, etc.). | February 12, 2005, 12:52 AM |
Invert | [quote author=quasi-modo link=topic=10504.msg99347#msg99347 date=1108164529] You should care about all browsers. I test sites on the following: IE6, IE5.5, IE5, IE4, GECKO (NS and MOZ), Opera, Lynx. Now I am not really concerned so much with how it looks on some of those, but I am concerned with it working. I just want to make sure that someone on any given platform can get to my content. I am not going to hack the heck out of my layout for one minor client because a few images are misaligned. [/quote] Um... no! I don't want to care and I will not care about people using older browsers. I don't want those people to go to my website anyway. Caring about browsers that don't comply with standards promotes companies to not care about standards. They will just say "Its ok, let the web developer stress to make our browser work." That's how Microsoft used to think, look at how many people use the illegal scroll bar elements, because IE supports it. Wrong answer! | February 12, 2005, 4:13 AM |
peofeoknight | [quote author=dxoigmn link=topic=10504.msg99356#msg99356 date=1108169576] [quote author=quasi-modo link=topic=10504.msg99297#msg99297 date=1108144976] xhtml is not more accessible than html, infact the opposite is true. The reason is xhtml is still new and our browsers are not handleing it all the same way. Basically xhtml can never be more accessible then html, it can be as accessible, but never more. I am using a mix of both html and xhtml, but I think that for the time being it is probably best to use 4.01 strict. [/quote] They're more accessible than most HTML 4.01 pages. When you start mixing design with data then it becomes harder for a browser to present the page to someone who is blind or someone using a cellphone. Using XHTML + CSS allows you to specify certain stylesheets for different medias (i.e. cell phones/pdas, printing, screen, etc.). [/quote] XHTML by it's self is not more accessible then html 4.01. If you use html 4.01 with css it is as accessible as you can get. Xhtml can be as accessible, but never any more accessible. | February 14, 2005, 2:06 AM |
peofeoknight | [quote author=Invert link=topic=10504.msg99377#msg99377 date=1108181610] [quote author=quasi-modo link=topic=10504.msg99347#msg99347 date=1108164529] You should care about all browsers. I test sites on the following: IE6, IE5.5, IE5, IE4, GECKO (NS and MOZ), Opera, Lynx. Now I am not really concerned so much with how it looks on some of those, but I am concerned with it working. I just want to make sure that someone on any given platform can get to my content. I am not going to hack the heck out of my layout for one minor client because a few images are misaligned. [/quote] Um... no! I don't want to care and I will not care about people using older browsers. I don't want those people to go to my website anyway. Caring about browsers that don't comply with standards promotes companies to not care about standards. They will just say "Its ok, let the web developer stress to make our browser work." That's how Microsoft used to think, look at how many people use the illegal scroll bar elements, because IE supports it. Wrong answer! [/quote] Your website should work on all platforms, period. Consider this: There are plenty of browsers that were around before we even had css. I am not saying your site has to look the same for them, but you should make the content accessible for them. If you follow the WCAG it will. The whole idea behind making a webstie is so that people can get to your content, it is not good to exclude anyone. Microsoft's scroll bars are proprietary and most developers do not care about it at all, you are not forced to use their scroll bars, it just adds some extra flashy newb style to your site if you do use them. | February 14, 2005, 2:09 AM |
kamakazie | [quote author=quasi-modo link=topic=10504.msg99648#msg99648 date=1108346812] [quote author=dxoigmn link=topic=10504.msg99356#msg99356 date=1108169576] [quote author=quasi-modo link=topic=10504.msg99297#msg99297 date=1108144976] xhtml is not more accessible than html, infact the opposite is true. The reason is xhtml is still new and our browsers are not handleing it all the same way. Basically xhtml can never be more accessible then html, it can be as accessible, but never more. I am using a mix of both html and xhtml, but I think that for the time being it is probably best to use 4.01 strict. [/quote] They're more accessible than most HTML 4.01 pages. When you start mixing design with data then it becomes harder for a browser to present the page to someone who is blind or someone using a cellphone. Using XHTML + CSS allows you to specify certain stylesheets for different medias (i.e. cell phones/pdas, printing, screen, etc.). [/quote] XHTML by it's self is not more accessible then html 4.01. If you use html 4.01 with css it is as accessible as you can get. Xhtml can be as accessible, but never any more accessible. [/quote] You don't understand my point, maybe because I'm not explaining well enough. What I'm trying to say is HTML 4.01 encourages the mixing of document and style whereas XHTML + CSS encourages you to keep them separate. Because HTML 4.01 encourages this mixing, it becomes difficult to present to people using cell phones and those who are blind because those applications must parse through the crap and sort out the good stuff. | February 14, 2005, 6:30 AM |
peofeoknight | [quote author=dxoigmn link=topic=10504.msg99682#msg99682 date=1108362610] [quote author=quasi-modo link=topic=10504.msg99648#msg99648 date=1108346812] [quote author=dxoigmn link=topic=10504.msg99356#msg99356 date=1108169576] [quote author=quasi-modo link=topic=10504.msg99297#msg99297 date=1108144976] xhtml is not more accessible than html, infact the opposite is true. The reason is xhtml is still new and our browsers are not handleing it all the same way. Basically xhtml can never be more accessible then html, it can be as accessible, but never more. I am using a mix of both html and xhtml, but I think that for the time being it is probably best to use 4.01 strict. [/quote] They're more accessible than most HTML 4.01 pages. When you start mixing design with data then it becomes harder for a browser to present the page to someone who is blind or someone using a cellphone. Using XHTML + CSS allows you to specify certain stylesheets for different medias (i.e. cell phones/pdas, printing, screen, etc.). [/quote] XHTML by it's self is not more accessible then html 4.01. If you use html 4.01 with css it is as accessible as you can get. Xhtml can be as accessible, but never any more accessible. [/quote] You don't understand my point, maybe because I'm not explaining well enough. What I'm trying to say is HTML 4.01 encourages the mixing of document and style whereas XHTML + CSS encourages you to keep them separate. Because HTML 4.01 encourages this mixing, it becomes difficult to present to people using cell phones and those who are blind because those applications must parse through the crap and sort out the good stuff. [/quote] HTML does not force you to mix style with structure though. My point is browser support of xhtml is not all that wonderful. It is as accessible as html at best, but can never be better. | February 14, 2005, 11:40 AM |
kamakazie | [quote author=quasi-modo link=topic=10504.msg99694#msg99694 date=1108381218] HTML does not force you to mix style with structure though. My point is browser support of xhtml is not all that wonderful. It is as accessible as html at best, but can never be better. [/quote] I never said HTML forces you to mix style and structure so that has no relevance what-so-ever. It may not force you but it certainly encourages you too mix the two. There's no need for you to have a point. I stated a simple fact and you turned it into an argument by telling me something I agree with. Meanwhile, I'm here trying to explain to you that your argument has nothing to do with what I said. | February 14, 2005, 8:17 PM |
Mitosis | Is it <i> bad </i> to style tables? Check the source on my page, www.dark-wire.net/sh/newd.html That's all I know how to do webcoding...Is it worth getting into the new stufF? | February 14, 2005, 9:58 PM |
Grok | [quote author=quasi-modo link=topic=10504.msg99649#msg99649 date=1108346989] Your website should work on all platforms, period.[/quote] Here is where we fundamentally disagree, and if on the fundamentals we stay in disagreement, our philosophies on web development will stay opposed. I believe I should engineer my sites and write my code to internet standards, as strict as possible. This actually increases site portability and usability. Web pages are not screens, and should not be treated as such. CSS differentiates device types, which is why it is separate from document content and structure. | February 14, 2005, 10:10 PM |
peofeoknight | [quote author=Grok link=topic=10504.msg99747#msg99747 date=1108419029] [quote author=quasi-modo link=topic=10504.msg99649#msg99649 date=1108346989] Your website should work on all platforms, period.[/quote] Here is where we fundamentally disagree, and if on the fundamentals we stay in disagreement, our philosophies on web development will stay opposed. I believe I should engineer my sites and write my code to internet standards, as strict as possible. This actually increases site portability and usability. Web pages are not screens, and should not be treated as such. CSS differentiates device types, which is why it is separate from document content and structure. [/quote] How are we disagreeing? | February 15, 2005, 6:37 PM |
peofeoknight | [quote author=dxoigmn link=topic=10504.msg99734#msg99734 date=1108412276] [quote author=quasi-modo link=topic=10504.msg99694#msg99694 date=1108381218] HTML does not force you to mix style with structure though. My point is browser support of xhtml is not all that wonderful. It is as accessible as html at best, but can never be better. [/quote] I never said HTML forces you to mix style and structure so that has no relevance what-so-ever. It may not force you but it certainly encourages you too mix the two. There's no need for you to have a point. I stated a simple fact and you turned it into an argument by telling me something I agree with. Meanwhile, I'm here trying to explain to you that your argument has nothing to do with what I said. [/quote] [quote]They're more accessible than most HTML 4.01 pages.[/quote] You quoted me originally saying that xhtml pages are more accessible than most html pages. Document style with css has nothing to do with it. Xhtml is pointless to use right now as it is not more accessible then html. That is what I have been trying to communicate in my posts. | February 15, 2005, 6:44 PM |
peofeoknight | [quote author=Mitosis link=topic=10504.msg99745#msg99745 date=1108418320] Is it <i> bad </i> to style tables? Check the source on my page, www.dark-wire.net/sh/newd.html That's all I know how to do webcoding...Is it worth getting into the new stufF? [/quote] It is bad to use tables in general for layout purposes. I have nothign against the use of a style sheet with a table... I have something against markup that is not semantically correct. The table is perfectly fine when it is used for what it was originally intended for... tabular data. | February 15, 2005, 6:47 PM |