<?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: Remote Debugging JavaScript</title>
	<atom:link href="http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 14:32:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: robcee</title>
		<link>http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/#comment-6373</link>
		<dc:creator>robcee</dc:creator>
		<pubDate>Wed, 28 May 2008 18:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=269#comment-6373</guid>
		<description>I've tinkered with MozRepl before and it was pretty cool. It was one of the main reasons I decided jssh wasn't terribly necessary to bring forward into Firefox2. Also, talking with Shaver about some of the event loop interactions jssh introduced made me wish for a better solution.

Props to Shane for SdConnect!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tinkered with MozRepl before and it was pretty cool. It was one of the main reasons I decided jssh wasn&#8217;t terribly necessary to bring forward into Firefox2. Also, talking with Shaver about some of the event loop interactions jssh introduced made me wish for a better solution.</p>
<p>Props to Shane for SdConnect!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Sullivan</title>
		<link>http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/#comment-6357</link>
		<dc:creator>Kim Sullivan</dc:creator>
		<pubDate>Mon, 26 May 2008 08:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=269#comment-6357</guid>
		<description>How about implementing Opera's Scope protocol, any plans for that? I know it's not finished and publicized yet (unless I missed something), but if browser vendors converged on a single technology, I think that everyone would win (being able to remotely debug one and the same javascript application running in several different browsers using the same tools).</description>
		<content:encoded><![CDATA[<p>How about implementing Opera&#8217;s Scope protocol, any plans for that? I know it&#8217;s not finished and publicized yet (unless I missed something), but if browser vendors converged on a single technology, I think that everyone would win (being able to remotely debug one and the same javascript application running in several different browsers using the same tools).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mihai Sucan</title>
		<link>http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/#comment-6356</link>
		<dc:creator>Mihai Sucan</dc:creator>
		<pubDate>Mon, 26 May 2008 07:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=269#comment-6356</guid>
		<description>I would suggest that the analysis for building remote JavaScript debuggers also includes the &lt;a href="http://dev.opera.com/articles/view/opera-dragonfly-architecture/" rel="nofollow"&gt;Scope API&lt;/a&gt;, provided by Opera Software, used by Dragonfly.

It would be certainly very interesting if people could talk about browser "interoperability" in the context of debugging Web applications. Implementing a single specification, like the Scope API spec, would be a start.

Additionally, the Scope API does not limit itself to remote JS debugging. It also allows full document inspection - DOM, CSS, and more. It's quite an interesting project.</description>
		<content:encoded><![CDATA[<p>I would suggest that the analysis for building remote JavaScript debuggers also includes the <a href="http://dev.opera.com/articles/view/opera-dragonfly-architecture/" rel="nofollow">Scope API</a>, provided by Opera Software, used by Dragonfly.</p>
<p>It would be certainly very interesting if people could talk about browser &#8220;interoperability&#8221; in the context of debugging Web applications. Implementing a single specification, like the Scope API spec, would be a start.</p>
<p>Additionally, the Scope API does not limit itself to remote JS debugging. It also allows full document inspection - DOM, CSS, and more. It&#8217;s quite an interesting project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Wilsher</title>
		<link>http://starkravingfinkle.org/blog/2008/05/remote-debugging-javascript/#comment-6355</link>
		<dc:creator>Shawn Wilsher</dc:creator>
		<pubDate>Mon, 26 May 2008 04:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=269#comment-6355</guid>
		<description>I'm not a huge fan of the Firebug UI either to be honest :/</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a huge fan of the Firebug UI either to be honest :/</p>
]]></content:encoded>
	</item>
</channel>
</rss>
