New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension Support #35

Open
cretz opened this Issue Sep 12, 2017 · 5 comments

Comments

4 participants
@cretz
Owner

cretz commented Sep 12, 2017

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

@cretz cretz added the enhancement label Sep 12, 2017

@tonymiao2012

This comment has been minimized.

Show comment
Hide comment
@tonymiao2012

tonymiao2012 Sep 19, 2017

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?

tonymiao2012 commented Sep 19, 2017

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?

@tfont

This comment has been minimized.

Show comment
Hide comment
@tfont

tfont Sep 26, 2017

@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.

tfont commented Sep 26, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@terinjokes

terinjokes Sep 26, 2017

@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.

terinjokes commented Sep 26, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@cretz

cretz Sep 27, 2017

Owner

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 #34)
  • Chromium plugin - same as Chrome, e.g. flash, widevine, etc (other issues like #30)

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

Owner

cretz commented Sep 27, 2017

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 #34)
  • Chromium plugin - same as Chrome, e.g. flash, widevine, etc (other issues like #30)

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

@tonymiao2012

This comment has been minimized.

Show comment
Hide comment
@tonymiao2012

tonymiao2012 Sep 27, 2017

@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.

tonymiao2012 commented Sep 27, 2017

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment