GreaseMonkey support

[johnd0e]

• GM is known to require special support
  • https://github.com/IITC-CE/ingress-intel-total-conversion/pull/51#issuecomment-459994380
• GM4 is not compatible with many scripts: #1264, #1245. There was PR #1249 (merged) meant to fix compatibility, but I am not sure yet if it is enough for plugins.

[modos189]

I use GreaseMonkey on a regular basis, everything is OK

[johnd0e]

GM v4? Great.

I have to install it too, in order to resolve #51.

[modos189]

Yes, v4.7.

Previously added this fix to work.

[johnd0e]

As step to more native support of GM, we can consider some iitc api extensions.

1. Eliminate window object usage (outside of setup). The only thing that is absolutely needed: fair way to transfer plugin's setup to common context (currently it's done via bootPlugins array).

   • Instead of script node injection we may consider to postMessage with the same stringified wrapper. The message should be processed then under full control of the main iitc script.

2. Existent plugins could be make compatible with new scheme just by replacing wrapper code. Bare minimum: window must be defined in wrapper as private empty object, and then attached to setup as it's property.

   Like this

   ```iitc-plugin.user.js (function (window) { // ... function setup (iitc, window) { // ... } // ... setup.window = window; }({})) ```

3. Actual IITC api can be passed to setup as parameter.

   Like this

   ```total-conversion-build.user.js // ... var setup = bootplugins[i]; L.extend(commonWindow, setup.window); try { setup(iitc, commonWindow); } catch (e) { // ... } ```

It is breaking change, as we need to all existent plugins. But:

• IITCm stays compatible in any case, as it doesn't use wrapper code. The same we can do in IITC-Button.
• Desktop: we can leave compatibility shim for plugins with old-wrapper.
• We can provide webservice to replace wrapper automatically. I suppose even IITC main script could be able to do it.