Adds an example extension to demonstrate the processes experimental API....

Adds an example extension to demonstrate the processes experimental API.

The extension adds a browser action that can list all the tabs that share a
renderer process with the current tab.

BUG=32303
TEST=Install show_tabs as an extension.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=39136

[Charlie Reis, 2010-02-16 17:14:50]

Here's a demo of how the processes API can be used.  (I'm looking into adding
more of the API, but just haven't gotten to it yet.)

I borrowed a generic icon from another example extension.

Any ideas how to bring a window to the front?  I was able to select a different
tab in the current window, but not change windows.

[rafaelw, 2010-02-16 19:13:30]

lgtm. sadly, there's no way to focus a window right now. crbug.com/31434. Looks
as though aaron has tried twice to land a fix. i'm not sure what the status is.
you may want to ping him.

http://codereview.chromium.org/606061/diff/1/2
File chrome/common/extensions/docs/examples/api/processes/show_tabs/popup.html
(right):

http://codereview.chromium.org/606061/diff/1/2#newcode13
chrome/common/extensions/docs/examples/api/processes/show_tabs/popup.html:13:
["<b>Tabs in Process ", process.id, ":</b>"].join("");
out of curiosity, why are you using [...].join("") construction, rather than
just " " + " " ..."

[Charlie Reis, 2010-02-16 19:42:10]

Thanks.  I put in a note about 31434 so that we can update this when it gets
fixed.

I'll go ahead and land it after lunch unless you see anything else.

http://codereview.chromium.org/606061/diff/1/2
File chrome/common/extensions/docs/examples/api/processes/show_tabs/popup.html
(right):

http://codereview.chromium.org/606061/diff/1/2#newcode13
chrome/common/extensions/docs/examples/api/processes/show_tabs/popup.html:13:
["<b>Tabs in Process ", process.id, ":</b>"].join("");
On 2010/02/16 19:13:30, rafaelw wrote:
> out of curiosity, why are you using [...].join("") construction, rather than
> just " " + " " ..."

I'd seen it in some other extensions (e.g., tabs/screenshot/screenshot.js), and
I thought I'd heard something about it being worthwhile for performance.  Turns
out that was an IE thing, and WebKit actually seems to be quicker on +.

I'll go ahead and change it, mainly because + is a bit easier to read.