Skip to content
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

Questions #81

Open
akrymski opened this issue Nov 28, 2020 · 3 comments
Open

Questions #81

akrymski opened this issue Nov 28, 2020 · 3 comments

Comments

@akrymski
Copy link

Interesting project! Not an issue, but thought I'd use this space to ask a question, cause where else? What's the reason for going with CEF instead of using Electron or forking Chromium like MS Edge did? My understanding is that CEF isn't really designed as a general purpose browser but more for spotify's use as a desktop app?

@cretz
Copy link
Owner

cretz commented Nov 28, 2020

CEF gives me much more power over Chromium than anything else and works with Qt which was a requirement for me since I needed advanced widgets. Electron gives much less flexibility. Direct or forked use of Chromium would have required me to essentially do the same as CEF - make it easily embeddable. I am one person, not Microsoft.

CEF is absolutely designed for general purpose use and has many uses beyond Spotify's specific use. It is perfect for general browser usage, and in my experience may be the best framework out there for doing so.

@akrymski
Copy link
Author

Interesting - what does CEF let you do that Electron doesn't?

@cretz
Copy link
Owner

cretz commented Nov 30, 2020

Primarily, I needed to native OS window handles to handle the Chrome windows as Qt widgets. Beyond that, you can look at the CEF headers and the Electron API to do other comparisons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants