CEF from Swift

[jjconti]

Hi, how can I use CEF from Apple Swift programming language? Swift can use classes written in objective-C.

[daka1]

I guess so... but why

[jjconti]

I guess so... but why

I'm writing an app in Swift and need and embedded browser. That's why.

[ed123]

I'm writing an app in Swift and need and embedded browser. That's why.

Why don't you use WebView instead? Unless you need features that only exist in Chrome?

[jjconti]

I want to have cookies not shared by all the OS. I want to be able to save them to a file an retrieve them in future runs of the programa. WebView can't do this. CEF does.

Is anyone going to give a answered instead of question the question?

[magreenblatt]

I want to have cookies not shared by all the OS. I want to be able to save them to a file an retrieve them in future runs of the programa. WebView can't do this. CEF does.

Is anyone going to give a answered instead of question the question?

I don't think anyone has tried it yet. You can be the trail blazer .

[derektran]

Hey jjconti,

Have you had success with this yet? I'm in the same exact situation and need to use non WebKit functionality (WebRTC video). Chromium's CEFClient app seems to work with it. However, I don't know how to import this into a new Swift project. If you've figured it out, I'd appreciate the tips!

[jjconti]

No yet.

[tml]

You may want to take a look at my Swift wrapper of CEF3: https://github.com/lvsti/CEF.swift

It's still incomplete, untested, and most likely unstable, but it may already work for toy projects, and it is under active development. It follows a different approach than most of the answers I've read in this forum: instead of wrapping C++ in ObjC and that in Swift, my framework wraps the CEF CAPI directly (which in fact wraps the CEF C++ core). The reason I chose this path was that I wanted to avoid the proliferation of @objc attributes all over the place in the Swift host app.

In this first phase, the plan is to have most of the API wrapped somehow (=for now, manually and mechanically). Later on, I'll try to generate as much of the glue code as possible, and will also rewrite the interface in a more Swift-y style (closures instead of one-method handlers, conformance of value types to various standard library protocols, etc.)

Feel free to submit issues and suggestions on github.