You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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?
The text was updated successfully, but these errors were encountered: