Issue 4028 - Add support for Edge extensions to buildtools

docs/metadata.edge.example

Index: docs/metadata.edge.example
===================================================================
new file mode 100644
--- /dev/null
+++ b/docs/metadata.edge.example
@@ -0,0 +1,71 @@
+[default]
+# Base metadata file whose sections and keys we inherit but can override.
+inherit = metadata.common
+
+# App identity assigned by the Windows Dev Center.
+[package_identity]
+name = ACME.MyExt

[Sebastian Noack, 2016/07/13 18:10:37]

I just noticed, this setting is redundant. The part before the dot is redundant
with "author" in the "general" section. And the part after the dot can be
retrieved from "name" message in the source translation. Just remove any spaces.

[Vasily Kuznetsov, 2016/10/04 14:46:45]

If I understand correctly this thing is more like an id. I think it might be
useful to have it here explicitly so it doesn't get messed up because of changes
to UI text.

[Sebastian Noack, 2016/10/04 19:58:03]

Frankly, I'm not sure whether the Windows Store would except a build that uses a
different name than has been reserved on the store and is the part of this
generated ID. Same for the author.

If it in fact doesn't have to be the same, I see your point. But even then one
could argue, that it would be most likely an accident if it's inconsistent, and
therefore good to require it to be consistent.

Also I wonder whether it's worth to have a separate [package_identity] section.
For reference, on Firefox we also have a unique ID and it is under [general].
And "publisher" is just the unique ID for the "author" which is already under
[general].

What do you think?

[Vasily Kuznetsov, 2016/10/11 15:58:26]

Probably being consistent with Firefox is a good thing. I moved `name` and
`publisher` into [general] renaming them to `app_id` and `publisher_id` (that's
what they really are).

I also added a warning in case the `app_id` seems mismatched with `author` (from
the metadata) and `display_name` (from the default translation).

[Sebastian Noack, 2016/10/12 11:07:48]

Fair enough, for keeping the app ID, rather then auto generating it. Not sure
whether the warning is worth the extra complexity though.

[Vasily Kuznetsov, 2016/10/12 14:13:42]

Yeah, me neither, actually. I coded it just so we could see how it would look.
Happy to remove it if you think it's not worth it.

[Sebastian Noack, 2016/10/12 14:43:25]

I leave it up to you, but FWIW, no I don't think it's worth it.

[Vasily Kuznetsov, 2016/10/13 11:56:35]

Me neither. Done

+publisher = CN=4F066043-8AFE-41C9-B762-6C15E77E3F88
+
+# Icons to be placed into /Assets and referenced in AppxManifest.xml.
+[appx_assets]
+# 50x50 logo for the store.
+logo_50.png = path/to/logo_50.png
+
+# 44x44 and 150x150 logos for Windows UI.
+logo_44.png = path/to/logo_44.png
+logo_150.png = path/to/big_logo.png
+
+[compat]
+# Target Edge version (for manifest.json)
+edge = 37.14332.1000.0
+# Min/max windows version (for AppxManifest.xml)
+windows = 10.0.14332.0/12.0.0.0
+
+[general]
+# Base name of the plugin file (version and extension will be added to this).
+basename = myext-edge
+
+# Display name and description for the manifest files.
+display_name = MyExt
+description = MyExt is the greatest extension

[Sebastian Noack, 2016/07/13 18:10:38]

This is redundant as well. The description can be retrieved from the source
translation.

[Vasily Kuznetsov, 2016/10/04 14:46:44]

Done

+
+# Background color for the Appx manifest.
+background_color = pink
+
+# Extension ID for Appx manifest.
+extension_id = 1.0

[Sebastian Noack, 2016/07/13 18:10:37]

This can be hard-coded to 1.0 in the template. Since there is only one entry
point it doesn't have any effect anyway.

[Sebastian Noack, 2016/09/13 10:41:23]

This attribute just changed, for Edge extensions it has to be set to
"EdgeExtension", rather than being floating point number, now. Even less useful
it is to have it configurable.

[Vasily Kuznetsov, 2016/10/04 14:46:44]

Done.

+
+# Permissions of the extension to place into manifest.json
+# (see https://developer.chrome.com/extensions/declare_permissions).
+permissions =
+  tabs
+  bookmarks
+  http://*/*
+  https://*/*
+
+# UI definitions.
+options = options.html
+devtools = devtools.html
+
+# Icon for the browser toolbar. Used to produce browser_action key in
+# manifest.json (see https://developer.chrome.com/extensions/browserAction).
+browserAction = icons/icon-19.png icons/icon-38.png popup.html
+
+# Icons for manifest.json.
+icons = icon-16.png icon-32.png icon-48.png icon-64.png icon-128.png
+
+# Schema for managed storage (storage.managed_schema in manifest.json).
+managedStorageSchema = schema.json

[Sebastian Noack, 2016/07/13 18:10:37]

Since Edge doesn't support managed storage (the key in the generated
manifest.json is ignored) it's rather misleading to document it here. Same for
the devtools option above. Or perhaps, just change the name of this file to be
platform agnostic.

[Vasily Kuznetsov, 2016/10/04 14:46:45]

Making this example platform agnostic is more complicated since different
metadata files have different keys. I'll keep it simple and remove the redundant
stuff.

Done.

+
+# Files that are renamed/moved when placed into the package.
+[mapping]
+target/path/file.png = source/path/icon.png
+
+# Javascript source files to be compiled/bundled by JSHydra.
+[convert_js]
+# Two files bundled into one.
+path/bundle.js = source/path/src1.js src2.js
+
+# Remove a file from a bundle defined in common.metadata.
+path/common-bundle.js -= removed/src.js