8000 Questions · Issue #81 · cretz/doogie · GitHub
[go: up one dir, main page]

Skip to content

Questions #81

Open
Open

Description

@akrymski

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?

Activity

  1. cretz commented on Nov 28, 2020

    @cretz
    Owner

    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.

  2. akrymski commented on Nov 28, 2020

    @akrymski
    Author

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

  3. cretz commented on Nov 30, 2020

    @cretz
    Owner

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0