Quote:
|
Originally Posted by activemx
Xhmtl is same as HTML with more strict syntax. This basically means that you are following the W3C standards and your code is strict to that standard. Nowdays, browsers are more forgiving so you dont necessarily need to use XHTML style.
|
I was curious more of why you use it over HTML - I know what it is.
Quote:
|
Originally Posted by jonathan lall
However, in theory, XHTML is an XML-based reformation of HTML, which means you can stick XML into it in an interoperable way. Writing in XHTML now is also future-friendly, because it's well-formed XML and thus it is eXtensible; for example, elements can be added just by changing the DTD and namespace. In a broad sense, this, and the more strict nature of XHTML forces standardization across websites and by browser engineers. Non-transitional XHTML encourages cleaner, more semantically-friendly code because it not only explicitly defines elements (you must close all your tags or the browser will not display anything, IE excepted of course, because it's stupid), but it makes your markup structural in nature, leaving presentation to CSS and other things such as (god, no) Javascript. I should note that the XML DOM is different, so much of your HTML Javascript, especially the presentational stuff, won't work with XHTML.
|
Thanks, I've been trying to write correct HTML 4.01 Transitional before moving onto XHTML (since I don't know any XML it wouldn't help me much). Unfortunatly...it seems every tutorial teaches you the wrong way to write HTML and every browsers parses the wrong way! Its a conspiracy against the W3C!
Quote:
|
Originally Posted by sanddrag
No one has addressed frames yet. I like to keep the balance at no frames. Frames are horrible. Google doesn't like them either. Flash is okay but only in small quantities. It should not be used for navigation.
|
Very good point! While you're all there saying JS is the devil...I feel frames are the devil! They look bad, scrolling gets weird in them, you can't truly add to your favorites with them, some browsers show them differently, etc. Theres nothing good about them (except for showing nav...but its better to use the require_once() PHP function to include navigation).
Now what about iframes? I think they're just as bad -
usually. Occasionally I see a site that just looks amazing with them, but besides that they usually look horrible!