S
Scruff
Why do any of the "elitist" web designers regard FP as a creator of dirty
html?
What does than mean, and is it true?
Thanks
html?
What does than mean, and is it true?
Thanks
Poor answer.Thomas A. Rowe said:Ask the "elitist" to define "Dirty HTML"
verification engines if is doe not then the page is consideredMD Websunlimited said:Some folks believe that generated HTML should pass specific HTML
there are those things that are efficient but what good isdirty.
In my early days I learned a single lesson that has served me well --
CEO of a company needs a report, it may be efficient tosomething that is efficient but is not effective. An example would be the
processing but then it would not be very effective if yourun the report when all reports are ran instead of stopping some other
wish to respond to the CEO.
The bottom line is if it works on your target audience then it is an
the task at hand accomplished ;>)effective page; it may have to many said:that and it may take an extra two seconds to display but who cares.
P.S. I believe you'll also find that those same folks take longer to get
the task at hand accomplished ;>)
Thomas A. Rowe said:It is not a poor answer, as the people that say FP generates "Dirty HTML" should be able to explain
exactly what they mean by the statement, and should be able to support it, which would have
eliminate you coming here to ask what they meant.
Mike did provide a good answer, however that is his take on what they meant, to truly know what they
meant, means you would have to ask those that made the statement.
So like Mike said, if it adds an extra second or two, so what?Murray said:I disagree. I understand the standards (sorta) and code to them. I test,
but not over the top. My pages are finished in half the time they required
before I took the time to understand the benefits of standards coding.
However - in my mind, "dirty HTML" means more than code that doesn't
validate - it means code that contains frank errors. These errors may not
be seen in a browser, and they many not cause error messages, but they are
nasty, ew, dirty anyway. I mean things like this -
<td align=right><a href="foo.html">link</a></font></td>
There are two errors there - a) an attribute without quotes, and b) a
terminating tag without the corresponding opening tag. Why worry about
this? Well, for me, every byte of weight is something I jealously guard. A
nasty tag adds weight to the page. It MUST come out.
Earlier versions of FP were rather legendary for doing things like this. FP
2003 can produce completely clean pages if you let it.
David Baxter said:Okay, then try this as an answer:
I've never heard the specific term "dirty HTML" and I don't know what
that means. The usual term used to criticize FP is "code bloat" or "HTML
bloat". As I have said on numerous occasions, this is virtually always
said by people who have never used FP or even opened the box -- it's a
myth propagated mostly by DreamWeaver zealots (not that there is
anything wrong with DreamWeaver but there is a lot wrong with zealots).
FP does not produce code that is any more bloated or any less clean than
any other WYSIWYG editor. Those who say it does are propagating a myth,
pure and simple, and an inaccurate one at that.
to which you so eloquently answered "go ask an elitist". That is certainly"Why do any of the "elitist" web designers regard FP as a creator of
dirty html? What does than mean, and is it true?
Thanks"