<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: innerHTML vs. DOM = pot noodles vs. real cooking</title>
	<atom:link href="http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/</link>
	<description>Chris Heilmann - Accessibility, Web Development and Pragmatism - can talk, will travel</description>
	<pubDate>Mon, 06 Oct 2008 18:48:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Craig</title>
		<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/#comment-6773</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Wed, 19 Dec 2007 17:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/?p=270#comment-6773</guid>
		<description>You might be interested in a technique I've devised as an alternative to innerHTML. It still allows you to pass an HTML string, but your code is validated and inserted into the DOM using safe W3C methods. It uses XML and only requires 50 lines of code.

For details, please visit:
http://www.optimalworks.net/blog/2007/web-development/javascript/innerhtml-alternative</description>
		<content:encoded><![CDATA[<p>You might be interested in a technique I&#8217;ve devised as an alternative to innerHTML. It still allows you to pass an <span class="caps">HTML </span>string, but your code is validated and inserted into the <span class="caps">DOM </span>using safe <span class="caps">W3C </span>methods. It uses <span class="caps">XML </span>and only requires 50 lines of code.</p>
<p>For details, please visit:<br />
<a href="http://www.optimalworks.net/blog/2007/web-development/javascript/innerhtml-alternative" rel="nofollow">http://www.optimalworks.net/blog/2007/web-development/javascript/innerhtml-alternative</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/#comment-4264</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Tue, 06 Mar 2007 07:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/?p=270#comment-4264</guid>
		<description>innerHTML is like paying for a hooker and DOM is like taking out a chick and trying to score.</description>
		<content:encoded><![CDATA[<p>innerHTML is like paying for a hooker and <span class="caps">DOM </span>is like taking out a chick and trying to score.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Marr</title>
		<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/#comment-3286</link>
		<dc:creator>Richard Marr</dc:creator>
		<pubDate>Thu, 12 Oct 2006 15:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/?p=270#comment-3286</guid>
		<description>I've been working on a big Javascript app for a major software company for about a year and a half. I found DOM methods to be slow and make my code less readable.

I really say this is yet another case where people should just use the right tool for the right job, but instead start talking about which is "right" and which is "wrong".</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been working on a big Javascript app for a major software company for about a year and a half. I found <span class="caps">DOM </span>methods to be slow and make my code less readable.</p>
<p>I really say this is yet another case where people should just use the right tool for the right job, but instead start talking about which is &#8220;right&#8221; and which is &#8220;wrong&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uli</title>
		<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/#comment-2310</link>
		<dc:creator>Uli</dc:creator>
		<pubDate>Thu, 27 Apr 2006 02:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/?p=270#comment-2310</guid>
		<description>Chris,
greetings. I was looking at your fabulous library of scripts, and I was wondering if it were ok to use one of yours for one of my clients. She's planning to sell stuff on her site, and I thought that your "YADM - Yet Another Dynamic Menu" would make for a nice navigation. As your copyright states, you would like to be asked when using your scripts for a commercial website.

As a webdesigner, I am always trying to showcase nice work where appropriate, so if it is ok by you, I would highlight your menu work on my website (iserlohdesign.com), so that other designers become aware of your work. Again, I am looking to use your script on a single site for a single client. thanks. 

Uli</description>
		<content:encoded><![CDATA[<p>Chris,<br />
greetings. I was looking at your fabulous library of scripts, and I was wondering if it were ok to use one of yours for one of my clients. She&#8217;s planning to sell stuff on her site, and I thought that your &#8220;YADM - Yet Another Dynamic Menu&#8221; would make for a nice navigation. As your copyright states, you would like to be asked when using your scripts for a commercial website.</p>
<p>As a webdesigner, I am always trying to showcase nice work where appropriate, so if it is ok by you, I would highlight your menu work on my website (iserlohdesign.com), so that other designers become aware of your work. Again, I am looking to use your script on a single site for a single client. thanks. </p>
<p>Uli</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves Gablin</title>
		<link>http://www.wait-till-i.com/2006/04/18/innerhtml-vs-dom-pot-noodles-vs-real-cooking/#comment-2281</link>
		<dc:creator>Yves Gablin</dc:creator>
		<pubDate>Fri, 21 Apr 2006 13:06:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/?p=270#comment-2281</guid>
		<description>This is an interesting topic :)
As a way to teach myself, I tried and created a simple "WYSIWYG" textarea editor (bold, italic...) in Javascript, and I worked hard to:
- only use the DOM,
- only use the resources of the current document (no external CSS, no external HTML page, and so on).

Conclusions:
- Even though it is possible not to use external resources, an IFrame sadly has to be created.
- To initialize the editor contents with the textarea contents, or put it back into the textarea, &lt;code&gt;&lt;b&gt;innerHtml&lt;/b&gt;&lt;/code&gt; and &lt;code&gt;document.&lt;b&gt;write()&lt;/b&gt;&lt;/code&gt; have to be used.

Those technologies are just too young in this area, and to date, building a whole stylesheet and content from the ground up, is impossible using only the DOM.

This apart, I'm rather satisfied with what I did: all else is 100% DOM.

Yves.</description>
		<content:encoded><![CDATA[<p>This is an interesting topic :)<br />
As a way to teach myself, I tried and created a simple &#8220;WYSIWYG&#8221; textarea editor (bold, italic&#8230;) in Javascript, and I worked hard to:<br />
- only use the <span class="caps">DOM,</span><br />
- only use the resources of the current document (no external <span class="caps">CSS, </span>no external <span class="caps">HTML </span>page, and so on).</p>
<p>Conclusions:<br />
- Even though it is possible not to use external resources, an IFrame sadly has to be created.<br />
- To initialize the editor contents with the textarea contents, or put it back into the textarea, <code>&lt;b&gt;innerHtml&lt;/b&gt;</code> and <code>document.&lt;b&gt;write()&lt;/b&gt;</code> have to be used.</p>
<p>Those technologies are just too young in this area, and to date, building a whole stylesheet and content from the ground up, is impossible using only the <span class="caps">DOM.</span></p>
<p>This apart, I&#8217;m rather satisfied with what I did: all else is 100% <span class="caps">DOM.</span></p>
<p>Yves.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
