<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DOMTool</title>
	<atom:link href="http://muffinresearch.co.uk/archives/2006/11/28/domtool/feed/" rel="self" type="application/rss+xml" />
	<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/</link>
	<description>the personal blog of Stuart Colville covering modern web development techniques and best practices</description>
	<lastBuildDate>Thu, 09 Feb 2012 02:58:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: 20 Useful Tools to Make Web Development More Efficient &#124; Graphic Techniques</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-66559</link>
		<dc:creator>20 Useful Tools to Make Web Development More Efficient &#124; Graphic Techniques</dc:creator>
		<pubDate>Sat, 21 May 2011 04:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-66559</guid>
		<description>[...] 9. DOMTool [...]</description>
		<content:encoded><![CDATA[<p>[...] 9. DOMTool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 20 Useful Tools to Make Web Development More Efficient &#124; 9Tricks.Com - Tips - Tricks - Tutorials</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-65340</link>
		<dc:creator>20 Useful Tools to Make Web Development More Efficient &#124; 9Tricks.Com - Tips - Tricks - Tutorials</dc:creator>
		<pubDate>Sat, 03 Oct 2009 03:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-65340</guid>
		<description>[...] 9. DOMTool [...]</description>
		<content:encoded><![CDATA[<p>[...] 9. DOMTool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis AlarcÃ³n, Blog &#187; Blog Archive &#187; 21 herramientas Ãºtiles para un desarrollo web mÃ¡s eficiente</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64720</link>
		<dc:creator>Luis AlarcÃ³n, Blog &#187; Blog Archive &#187; 21 herramientas Ãºtiles para un desarrollo web mÃ¡s eficiente</dc:creator>
		<pubDate>Tue, 09 Dec 2008 04:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64720</guid>
		<description>[...]  DOMTool fue creado para reducir el tiempo que tarda el cÃ³digo en estructuras DOM. DOM tiene opciones tan simples como copiar su cÃ³digo HTML en el DOMTool y a continuaciÃ³n, hacer clic en un botÃ³n. [...]</description>
		<content:encoded><![CDATA[<p>[...]  DOMTool fue creado para reducir el tiempo que tarda el cÃ³digo en estructuras DOM. DOM tiene opciones tan simples como copiar su cÃ³digo HTML en el DOMTool y a continuaciÃ³n, hacer clic en un botÃ³n. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seo Peru :: Recursos para Webmaster</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64499</link>
		<dc:creator>Seo Peru :: Recursos para Webmaster</dc:creator>
		<pubDate>Fri, 25 Jul 2008 15:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64499</guid>
		<description>[...] DOMTool   DOMTool fue creado para reducir el tiempo que tarda el código en estructuras DOM. DOM tiene opciones tan [...]</description>
		<content:encoded><![CDATA[<p>[...] DOMTool   DOMTool fue creado para reducir el tiempo que tarda el código en estructuras DOM. DOM tiene opciones tan [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 20ä¸ªæœ‰ç”¨çš„å·¥å…·è®©ä½ çš„webå¼€å‘æ›´æœ‰æ•ˆçŽ‡ï¼ˆ1ï¼‰ &#124; è€é»‘ä¸“ç”¨</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64442</link>
		<dc:creator>20ä¸ªæœ‰ç”¨çš„å·¥å…·è®©ä½ çš„webå¼€å‘æ›´æœ‰æ•ˆçŽ‡ï¼ˆ1ï¼‰ &#124; è€é»‘ä¸“ç”¨</dc:creator>
		<pubDate>Mon, 30 Jun 2008 08:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64442</guid>
		<description>[...] 9. DOMTool [...]</description>
		<content:encoded><![CDATA[<p>[...] 9. DOMTool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 20ä¸ªè®©ä½ webå¼€å‘æ›´å…·æ•ˆçŽ‡çš„å·¥å…·(ä¸Š) - è¸ç ´&#8217;BLOG</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64350</link>
		<dc:creator>20ä¸ªè®©ä½ webå¼€å‘æ›´å…·æ•ˆçŽ‡çš„å·¥å…·(ä¸Š) - è¸ç ´&#8217;BLOG</dc:creator>
		<pubDate>Thu, 29 May 2008 01:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64350</guid>
		<description>[...] 9. DOMTool [...]</description>
		<content:encoded><![CDATA[<p>[...] 9. DOMTool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Colville</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64329</link>
		<dc:creator>Stuart Colville</dc:creator>
		<pubDate>Sat, 17 May 2008 09:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64329</guid>
		<description>@Craig: looks exactly what Rajesh is looking for, nice work.

@Rajesh: Yes there&#039;s several utilities as part of framworks that are designed to do just that. However, the point of DOMTool was to provide a way to output the specific lines of code (albeit unoptimised) so that &lt;em&gt;you&lt;em&gt; the developer has full control over your code rather than handing off to a wrapper function to do it for you. Also parsing structures on the fly to then inject them using DOM methods will be slower due to the extra step involved. Again this is why offline conversion made sense.</description>
		<content:encoded><![CDATA[<p>@Craig: looks exactly what Rajesh is looking for, nice work.</p>
<p>@Rajesh: Yes there&#8217;s several utilities as part of framworks that are designed to do just that. However, the point of DOMTool was to provide a way to output the specific lines of code (albeit unoptimised) so that <em>you</em><em> the developer has full control over your code rather than handing off to a wrapper function to do it for you. Also parsing structures on the fly to then inject them using DOM methods will be slower due to the extra step involved. Again this is why offline conversion made sense.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64328</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Sat, 17 May 2008 08:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64328</guid>
		<description>I developed a JS function called BetterInnerHTML that does just that - you pass an HTML string, like you would with innerHTML, but it uses DOM node creation methods to create the content. It&#039;s therefore as easy to use as innerHTML but doesn&#039;t have the problems.

It&#039;s just 1Kb of code and available here:
&lt;a href=&quot;http://www.optimalworks.net/resources/betterinnerhtml/&quot; rel=&quot;nofollow&quot;&gt;http://www.optimalworks.net/resources/betterinnerhtml/&lt;/a&gt;

more details here:
&lt;a href=&quot;http://www.optimalworks.net/blog/2007/web-development/javascript/innerhtml-alternative&quot; rel=&quot;nofollow&quot;&gt;http://www.optimalworks.net/blog/2007/web-development/javascript/innerhtml-alternative&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I developed a JS function called BetterInnerHTML that does just that &#8211; you pass an HTML string, like you would with innerHTML, but it uses DOM node creation methods to create the content. It&#8217;s therefore as easy to use as innerHTML but doesn&#8217;t have the problems.</p>
<p>It&#8217;s just 1Kb of code and available here:<br />
<a href="http://www.optimalworks.net/resources/betterinnerhtml/" rel="nofollow">http://www.optimalworks.net/resources/betterinnerhtml/</a></p>
<p>more details here:<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: 20 Useful Tools to Make Web Development More Efficient &#124; Six Revisions</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-64325</link>
		<dc:creator>20 Useful Tools to Make Web Development More Efficient &#124; Six Revisions</dc:creator>
		<pubDate>Thu, 15 May 2008 01:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-64325</guid>
		<description>[...] 9. DOMTool [...]</description>
		<content:encoded><![CDATA[<p>[...] 9. DOMTool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajesh</title>
		<link>http://muffinresearch.co.uk/archives/2006/11/28/domtool/comment-page-1/#comment-37743</link>
		<dc:creator>Rajesh</dc:creator>
		<pubDate>Mon, 07 May 2007 07:04:13 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/11/28/domtool/#comment-37743</guid>
		<description>Is there a packaged version of this tool that can be used within an application on-the-fly for converting HTML blocks into DOM statements? Something like ...

  var theHTML = &quot;[p][strong]this is a test[/strong][/p]&quot;;
  var theDOM = DOMTool(theHTML);
  eval(theDOM);

Or maybe just...

  DOMTool(theHTML);

which could automatically call eval() at the end. How about that?</description>
		<content:encoded><![CDATA[<p>Is there a packaged version of this tool that can be used within an application on-the-fly for converting HTML blocks into DOM statements? Something like &#8230;</p>
<p>  var theHTML = &#8220;[p][strong]this is a test[/strong][/p]&#8220;;<br />
  var theDOM = DOMTool(theHTML);<br />
  eval(theDOM);</p>
<p>Or maybe just&#8230;</p>
<p>  DOMTool(theHTML);</p>
<p>which could automatically call eval() at the end. How about that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

