Extension Support

[cretz]

Now that this issue has gone a long way, we might be able to add them to Doogie soon. Yay.

[tonymiao2012]

As far as I know, CEF3 supports JS extension itself. Use 'native' tag to claim JS codes will map your JS functions to native methods. Why not use that way?

[travisfont]

@tonymiao2012 can you explain in better detail?

Also, what's the difference from Extension (to) Plugin? Reference #34

Overall, having extensions is a HUGE enhancement! It's what separates the user from fully using Doogie over Chrome.

[terinjokes]

@tfont I'm not @cretz but I believe plugins means the "native" plugins like Flash (and Widevine DRM plugin #30), whereas extensions are the things we are commonly interacting with.

[cretz]

My uses of the terms:

• extension - same as Chrome defines them, and hopefully same API (this issue)
• Doogie plugin - maybe some thing in the future where I expose C++ headers so you can write something that interacts with the page tree for example (issue Plugin Support #34)
• Chromium plugin - same as Chrome, e.g. flash, widevine, etc (other issues like Support Widevine DRM Plugin #30)

No guarantees if/when any of this will happen, but the issues are there to capture discussion.

[tonymiao2012]

@tfont Well, the meaning of "extension" I mentioned before is similar with the concept "JS Integration". I have a reference here: https://bitbucket.org/chromiumembedded/cef/wiki/JavaScriptIntegration.md. CEF3 supports embedded V8 extension. So you could define your local JS API freely.