Font Settings API: UI overhaul of example extension.

Font Settings API: UI overhaul of example extension.

Based on suggestions from UI review and Marcin Wichary.
This change copies several files required to use the list and overlay/popup
widgets of Chrome.

BUG=114805
TBR=mpcomplete

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=163241

[falken, 2012-10-22 06:22:44]

Hi Matt,

This is a UI overhaul of the example extension. All the new files are just
copied from resources/shared so the extension can use the UI widgets used in
Chrome options.

[Matt Perry, 2012-10-22 21:32:26]

LGTM.

If this is intended to be a component extension, it can access chrome://
resources directly, so you wouldn't need to make copies.

[falken, 2012-10-23 01:49:52]

Thanks for reviewing. Can you point me to documentation or other background
information about component extensions? Searching isn't providing much, I can
just see Extension::COMPONENT exists.

On 2012/10/22 21:32:26, Matt Perry wrote:
> LGTM.
> 
> If this is intended to be a component extension, it can access chrome://
> resources directly, so you wouldn't need to make copies.

[Matt Perry, 2012-10-23 01:52:47]

Not sure if there is documentation. A component extension is just one that is
bundled with chrome. It has extra privileges because it is considered part of
chrome.

On 2012/10/23 01:49:52, falken wrote:
> Thanks for reviewing. Can you point me to documentation or other background
> information about component extensions? Searching isn't providing much, I can
> just see Extension::COMPONENT exists.
> 
> On 2012/10/22 21:32:26, Matt Perry wrote:
> > LGTM.
> > 
> > If this is intended to be a component extension, it can access chrome://
> > resources directly, so you wouldn't need to make copies.

[falken, 2012-10-23 02:09:05]

I see. Does this mean the extension is always enabled (i.e., it's not in the Web
Store and can't be enabled/disabled in chrome://chrome/extensions)?

It might be a candidate for a component extension. I'll bring it up with UI
leads.

On 2012/10/23 01:52:47, Matt Perry wrote:
> Not sure if there is documentation. A component extension is just one that is
> bundled with chrome. It has extra privileges because it is considered part of
> chrome.
> 
> On 2012/10/23 01:49:52, falken wrote:
> > Thanks for reviewing. Can you point me to documentation or other background
> > information about component extensions? Searching isn't providing much, I
can
> > just see Extension::COMPONENT exists.
> > 
> > On 2012/10/22 21:32:26, Matt Perry wrote:
> > > LGTM.
> > > 
> > > If this is intended to be a component extension, it can access chrome://
> > > resources directly, so you wouldn't need to make copies.

[Matt Perry, 2012-10-23 18:15:21]

On 2012/10/23 02:09:05, falken wrote:
> I see. Does this mean the extension is always enabled (i.e., it's not in the
Web
> Store and can't be enabled/disabled in chrome://chrome/extensions)?

Yes. It doesn't show up in chrome:extensions either. The bookmark manager is a
component extension, for example.