<?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: WebKit Inspector wish list</title>
	<atom:link href="http://lensco.be/2010/04/15/webkit-inspector-wish-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/</link>
	<description>Thoughts on web design and all that jazz</description>
	<lastBuildDate>Mon, 03 Oct 2011 19:35:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Brian Grinstead &#187; Blog Archive &#187; Chrome Developer Tools Colorpicker Concept</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-388</link>
		<dc:creator>Brian Grinstead &#187; Blog Archive &#187; Chrome Developer Tools Colorpicker Concept</dc:creator>
		<pubDate>Mon, 03 Oct 2011 19:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-388</guid>
		<description>[...] I always thought it would be awesome to have a colorpicker in browser developer tools. Who wants to guess at hex colors or open up a separate program just to get a color code? Apparently I&#8217;m not the only one who thinks a colorpicker inside the developer toolbar would be nice. [...]</description>
		<content:encoded><![CDATA[<p>[...] I always thought it would be awesome to have a colorpicker in browser developer tools. Who wants to guess at hex colors or open up a separate program just to get a color code? Apparently I&#8217;m not the only one who thinks a colorpicker inside the developer toolbar would be nice. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mathias Bynens</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-340</link>
		<dc:creator>Mathias Bynens</dc:creator>
		<pubDate>Sun, 12 Sep 2010 12:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-340</guid>
		<description>Something I’d like to add to the wish list: Firebug’s console output is much better than the Web Inspector’s. There’s a bug for that here: &lt;a href=&quot;https://bugs.webkit.org/show_bug.cgi?id=44766&quot; rel=&quot;nofollow&quot;&gt;Web Inspector: color-code property values in object notation&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Something I’d like to add to the wish list: Firebug’s console output is much better than the Web Inspector’s. There’s a bug for that here: <a href="https://bugs.webkit.org/show_bug.cgi?id=44766" rel="nofollow">Web Inspector: color-code property values in object notation</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bram</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-307</link>
		<dc:creator>Bram</dc:creator>
		<pubDate>Sat, 17 Apr 2010 12:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-307</guid>
		<description>@pfeldman Awesome, that looks much more friendly to my eyes. Interface elements being in the way of the actual content have stopped me from using the webkit inspector up till today - and I want to bail out of firefox so badly right now. 

About displaying the browser style sheet or not: when we develop our css files (outside the browser) this is something we have to override by creating new styles. If you want to enable plain text editing of styles in the future, wouldn&#039;t it make sense to display the browser stylesheet seperately as well? We have to develop independant of the browser anyway.</description>
		<content:encoded><![CDATA[<p>@pfeldman Awesome, that looks much more friendly to my eyes. Interface elements being in the way of the actual content have stopped me from using the webkit inspector up till today &#8211; and I want to bail out of firefox so badly right now. </p>
<p>About displaying the browser style sheet or not: when we develop our css files (outside the browser) this is something we have to override by creating new styles. If you want to enable plain text editing of styles in the future, wouldn&#8217;t it make sense to display the browser stylesheet seperately as well? We have to develop independant of the browser anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-305</link>
		<dc:creator>Jose</dc:creator>
		<pubDate>Fri, 16 Apr 2010 20:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-305</guid>
		<description>&quot;What Firebug doesn’t have either, but which I’d deem very useful, is an integrated color picker. Both for sampling colors on the web page, and for selecting colors for properties.&quot;

You might want to try Firepicker, a simple color picker plugin for Firebug. It does that job so nicely I can&#039;t believe it took me so long to discover (just about a month ago)

Best part is, after discovering Firepicker and realizing that there are now plugins for Firebug, I went on the search. There are a couple more than those I listed below, but they weren&#039;t something I needed.

 - FireDiff (track changes in Firebug)
 - FireQuery (jQuery enhancements for Firebug)</description>
		<content:encoded><![CDATA[<p>&#8220;What Firebug doesn’t have either, but which I’d deem very useful, is an integrated color picker. Both for sampling colors on the web page, and for selecting colors for properties.&#8221;</p>
<p>You might want to try Firepicker, a simple color picker plugin for Firebug. It does that job so nicely I can&#8217;t believe it took me so long to discover (just about a month ago)</p>
<p>Best part is, after discovering Firepicker and realizing that there are now plugins for Firebug, I went on the search. There are a couple more than those I listed below, but they weren&#8217;t something I needed.</p>
<p> &#8211; FireDiff (track changes in Firebug)<br />
 &#8211; FireQuery (jQuery enhancements for Firebug)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pfeldman</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-304</link>
		<dc:creator>pfeldman</dc:creator>
		<pubDate>Fri, 16 Apr 2010 18:59:03 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-304</guid>
		<description>Thanks for putting this together. I think we can address most items if not all.

- I have a patch that reduces clutter: https://bug-36747-attachments.webkit.org/attachment.cgi?id=51948. Tell me if you like it.
- Showing subset of inherited styles is a tough one. We&#039;d like to move to editing CSS as text at some point. And it is great when the snippet being edited matches the source code. We need to think on how to solve this.
- Autocompletion - let&#039;s just do it
- Adding CSS Properties - see Joe&#039;s comments above
- Highlight color - same as autocompletion. Let&#039;s just fix
- Disable/enable to the left is tough due to expandable shorthands
- We should just take color picker from closure of something.</description>
		<content:encoded><![CDATA[<p>Thanks for putting this together. I think we can address most items if not all.</p>
<p>- I have a patch that reduces clutter: <a href="https://bug-36747-attachments.webkit.org/attachment.cgi?id=51948" rel="nofollow">https://bug-36747-attachments.webkit.org/attachment.cgi?id=51948</a>. Tell me if you like it.<br />
- Showing subset of inherited styles is a tough one. We&#8217;d like to move to editing <abbr title="Cascading Style Sheets">CSS</abbr> as text at some point. And it is great when the snippet being edited matches the source code. We need to think on how to solve this.<br />
- Autocompletion &#8211; let&#8217;s just do it<br />
- Adding <abbr title="Cascading Style Sheets">CSS</abbr> Properties &#8211; see Joe&#8217;s comments above<br />
- Highlight color &#8211; same as autocompletion. Let&#8217;s just fix<br />
- Disable/enable to the left is tough due to expandable shorthands<br />
- We should just take color picker from closure of something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-303</link>
		<dc:creator>Bart</dc:creator>
		<pubDate>Fri, 16 Apr 2010 18:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-303</guid>
		<description>I don&#039;t think WebKit will ever feel right to me until they fix the margin/padding coloring. Having it be all blue with borders around margin and padding just feels too confusing (is the border part of the border or the margin or the padding??).</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think WebKit will ever feel right to me until they fix the margin/padding coloring. Having it be all blue with borders around margin and padding just feels too confusing (is the border part of the border or the margin or the padding??).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate beaty</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-302</link>
		<dc:creator>nate beaty</dc:creator>
		<pubDate>Fri, 16 Apr 2010 17:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-302</guid>
		<description>Agree with all your points, especially how Firebug shows just the relevant styles by default, and also the handy color differences for margin/padding. This is probably 80% of what I use Firebug for, and it&#039;s unbelievably useful for quickly developing/debugging CSS.

If all I ever had was WebKit inspector I&#039;d probably be happy, but I&#039;ve been spoiled by Firebug.

I also find myself looking for a color picker often. It&#039;s one of the many things I love about TextMate, cmd-shift-c brings up the color in the picker, tweak it a bit and hit OK and it updates the CSS. Deluxe.</description>
		<content:encoded><![CDATA[<p>Agree with all your points, especially how Firebug shows just the relevant styles by default, and also the handy color differences for margin/padding. This is probably 80% of what I use Firebug for, and it&#8217;s unbelievably useful for quickly developing/debugging <abbr title="Cascading Style Sheets">CSS</abbr>.</p>
<p>If all I ever had was WebKit inspector I&#8217;d probably be happy, but I&#8217;ve been spoiled by Firebug.</p>
<p>I also find myself looking for a color picker often. It&#8217;s one of the many things I love about TextMate, cmd-shift-c brings up the color in the picker, tweak it a bit and hit OK and it updates the <abbr title="Cascading Style Sheets">CSS</abbr>. Deluxe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Mueller</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-301</link>
		<dc:creator>Patrick Mueller</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-301</guid>
		<description>Even if you can&#039;t help out with the implementation of your wish-list items, you can help out by opening bugs for each of your wish-list items.  To open a new bug against Web Inspector specifically, it&#039;s useful to use this link:

http://webkit.org/new-inspector-bug

Going through that link redirects you into Bugzilla with a bunch of stuff pre-filled for Web Inspector.

Looking forward to seeing your bugs!</description>
		<content:encoded><![CDATA[<p>Even if you can&#8217;t help out with the implementation of your wish-list items, you can help out by opening bugs for each of your wish-list items.  To open a new bug against Web Inspector specifically, it&#8217;s useful to use this link:</p>
<p><a href="http://webkit.org/new-inspector-bug" rel="nofollow">http://webkit.org/new-inspector-bug</a></p>
<p>Going through that link redirects you into Bugzilla with a bunch of stuff pre-filled for Web Inspector.</p>
<p>Looking forward to seeing your bugs!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Pecoraro</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-300</link>
		<dc:creator>Joseph Pecoraro</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-300</guid>
		<description>Inherited Styles - people seem to complain if we do have them and if we don&#039;t have them. Who knows what the best answer is!

Autocompletion - is an open bug actively being worked on by a new contributor:
https://bugs.webkit.org/show_bug.cgi?id=17374

Adding CSS Properties - Try pushing the Tab key. Try single click and pause. Try double clicking the white-space. Try editing the style attribute on the element. It works. We will need to improve discoverability in this area but for the most part the capability is there.</description>
		<content:encoded><![CDATA[<p>Inherited Styles &#8211; people seem to complain if we do have them and if we don&#8217;t have them. Who knows what the best answer is!</p>
<p>Autocompletion &#8211; is an open bug actively being worked on by a new contributor:<br />
<a href="https://bugs.webkit.org/show_bug.cgi?id=17374" rel="nofollow">https://bugs.webkit.org/show_bug.cgi?id=17374</a></p>
<p>Adding <abbr title="Cascading Style Sheets">CSS</abbr> Properties &#8211; Try pushing the Tab key. Try single click and pause. Try double clicking the white-space. Try editing the style attribute on the element. It works. We will need to improve discoverability in this area but for the most part the capability is there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: junkiesxl</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-299</link>
		<dc:creator>junkiesxl</dc:creator>
		<pubDate>Thu, 15 Apr 2010 21:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-299</guid>
		<description>Don&#039;t agree completely, however you did point out a deal breaker I wasn&#039;t aware of:
Not being able to add a CSS-style with a doubleclick seems strange (I always thought they added it, but the only way you can do it is to use the Gear menu and add a style, but that&#039;s not that clean a solution) .

Thanks !</description>
		<content:encoded><![CDATA[<p>Don&#8217;t agree completely, however you did point out a deal breaker I wasn&#8217;t aware of:<br />
Not being able to add a <abbr title="Cascading Style Sheets">CSS</abbr>-style with a doubleclick seems strange (I always thought they added it, but the only way you can do it is to use the Gear menu and add a style, but that&#8217;s not that clean a solution) .</p>
<p>Thanks !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idleberg</title>
		<link>http://lensco.be/2010/04/15/webkit-inspector-wish-list/#comment-297</link>
		<dc:creator>idleberg</dc:creator>
		<pubDate>Thu, 15 Apr 2010 21:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://lensco.be/?p=339#comment-297</guid>
		<description>i agree, the main reason i prefer firebug is the double-clicking to edit. what i dislike in firebug: it sometimes acts random. sometimes the console doesn&#039;t open or it lags, sometimes it&#039;s jumping between its tabs.

btw, i have read that you&#039;d be looking forward to switch entirely to safari. have you thought about chrome? there is firebug for chrome!</description>
		<content:encoded><![CDATA[<p>i agree, the main reason i prefer firebug is the double-clicking to edit. what i dislike in firebug: it sometimes acts random. sometimes the console doesn&#8217;t open or it lags, sometimes it&#8217;s jumping between its tabs.</p>
<p>btw, i have read that you&#8217;d be looking forward to switch entirely to safari. have you thought about chrome? there is firebug for chrome!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

