<?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: Firebug Feature? Tagged &#8216;firebugged&#8217;</title>
	<atom:link href="http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/</link>
	<description>Web Development Evolved</description>
	<lastBuildDate>Sun, 12 May 2013 09:29:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Albert</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-207</link>
		<dc:creator>Albert</dc:creator>
		<pubDate>Wed, 18 Feb 2009 08:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-207</guid>
		<description><![CDATA[A little, perhaps offtopic, proposal for changing the user experience. Personally, I think the users problem is in the difference between a global enable/disable, and a per-site enable/disable. I do not know if there are two &#039;camps&#039;, one that always wants Firebug turned on or off, and another that wants the per-site settings. But you pointed out that performance is unacceptable when turning Firebug panels on permanently.

So, my proposal is: remove the global enable/disable switch. This would clear up the dropdown in Firebugs tabs - you might get away with removing the dropdown fully, and replace it with a permanent &#039;enabled for this site&#039; checkbox which is much more discoverable.

This would also clean the site list: it would become a whitelist, no need to add disabled sites when there&#039;s no global enable.

I know this is a change that will remove behavior some people might rely on, but I believe its for the better. Love to hear comments!]]></description>
		<content:encoded><![CDATA[<p>A little, perhaps offtopic, proposal for changing the user experience. Personally, I think the users problem is in the difference between a global enable/disable, and a per-site enable/disable. I do not know if there are two &#8216;camps&#8217;, one that always wants Firebug turned on or off, and another that wants the per-site settings. But you pointed out that performance is unacceptable when turning Firebug panels on permanently.</p>
<p>So, my proposal is: remove the global enable/disable switch. This would clear up the dropdown in Firebugs tabs &#8211; you might get away with removing the dropdown fully, and replace it with a permanent &#8216;enabled for this site&#8217; checkbox which is much more discoverable.</p>
<p>This would also clean the site list: it would become a whitelist, no need to add disabled sites when there&#8217;s no global enable.</p>
<p>I know this is a change that will remove behavior some people might rely on, but I believe its for the better. Love to hear comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-143</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Sat, 07 Feb 2009 08:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-143</guid>
		<description><![CDATA[Wouldn&#039;t SQLite be faster than a plain text file? At least with SQLite the URLs could be indexed.]]></description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t SQLite be faster than a plain text file? At least with SQLite the URLs could be indexed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrianL</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-133</link>
		<dc:creator>BrianL</dc:creator>
		<pubDate>Thu, 05 Feb 2009 23:40:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-133</guid>
		<description><![CDATA[I haven&#039;t read the other comments, but I like the idea of being able to type &quot;firebugged&quot; in my address bar.  Keep up the great work John!]]></description>
		<content:encoded><![CDATA[<p>I haven&#8217;t read the other comments, but I like the idea of being able to type &#8220;firebugged&#8221; in my address bar.  Keep up the great work John!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jerone</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-125</link>
		<dc:creator>jerone</dc:creator>
		<pubDate>Wed, 04 Feb 2009 23:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-125</guid>
		<description><![CDATA[I&#039;m a very big fan of Firebug. Beside Firebug I&#039;m also a big user of Foxmarks.
And now comes the problem, every time I change a tag, Foxmarks registers this and what to synchronize. So every time I open Firebug you put a new tag there and Foxmarks gets busy.
I see this as a big disadvantage, which leads to a lot off busy servers at Foxmarks.
I vote for another solution.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m a very big fan of Firebug. Beside Firebug I&#8217;m also a big user of Foxmarks.<br />
And now comes the problem, every time I change a tag, Foxmarks registers this and what to synchronize. So every time I open Firebug you put a new tag there and Foxmarks gets busy.<br />
I see this as a big disadvantage, which leads to a lot off busy servers at Foxmarks.<br />
I vote for another solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Silvestri</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-119</link>
		<dc:creator>John Silvestri</dc:creator>
		<pubDate>Wed, 04 Feb 2009 17:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-119</guid>
		<description><![CDATA[P.S. Make that &#039;site-specific&#039; prefs.
(e.g. browser.zoom.siteSpecific)]]></description>
		<content:encoded><![CDATA[<p>P.S. Make that &#8216;site-specific&#8217; prefs.<br />
(e.g. browser.zoom.siteSpecific)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Silvestri</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-118</link>
		<dc:creator>John Silvestri</dc:creator>
		<pubDate>Wed, 04 Feb 2009 17:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-118</guid>
		<description><![CDATA[I use Firebug...but I don&#039;t use bookmarks.

I stopped using bookmarks many years ago, and strictly use the Awesomebar to get where I&#039;m trying to go.  (Before it&#039;s existence, I used to just type URL fragments...now life is easier.)

I&#039;d second the recommendation of using content-specific prefs - that&#039;s kind of what they were designed for, and are far less intrusive.]]></description>
		<content:encoded><![CDATA[<p>I use Firebug&#8230;but I don&#8217;t use bookmarks.</p>
<p>I stopped using bookmarks many years ago, and strictly use the Awesomebar to get where I&#8217;m trying to go.  (Before it&#8217;s existence, I used to just type URL fragments&#8230;now life is easier.)</p>
<p>I&#8217;d second the recommendation of using content-specific prefs &#8211; that&#8217;s kind of what they were designed for, and are far less intrusive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-110</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Wed, 04 Feb 2009 11:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-110</guid>
		<description><![CDATA[Doesn&#039;t Firebug already remember which pages it&#039;s open on, in order to show itself when a tab is selected (and list the active pages in the status bar tooltip)?]]></description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t Firebug already remember which pages it&#8217;s open on, in order to show itself when a tab is selected (and list the active pages in the status bar tooltip)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jigar Shah</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-108</link>
		<dc:creator>Jigar Shah</dc:creator>
		<pubDate>Wed, 04 Feb 2009 10:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-108</guid>
		<description><![CDATA[I have another suggestion. What if we enable only when FB panel / window is open ? So if you want to do some resource hungry operation open firebug panel. Here you don&#039;t have to remember urls :)]]></description>
		<content:encoded><![CDATA[<p>I have another suggestion. What if we enable only when FB panel / window is open ? So if you want to do some resource hungry operation open firebug panel. Here you don&#8217;t have to remember urls <img src='http://blog.getfirebug.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FP</title>
		<link>http://blog.getfirebug.com/2009/02/03/firebug-feature-tagged-firebugged/comment-page-1/#comment-104</link>
		<dc:creator>FP</dc:creator>
		<pubDate>Wed, 04 Feb 2009 08:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.getfirebug.com/?p=78#comment-104</guid>
		<description><![CDATA[You could also try using content prefs:

https://developer.mozilla.org/En/Using_content_preferences]]></description>
		<content:encoded><![CDATA[<p>You could also try using content prefs:</p>
<p><a href="https://developer.mozilla.org/En/Using_content_preferences" rel="nofollow">https://developer.mozilla.org/En/Using_content_preferences</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
