Replies: 1 comment
-
Not currently. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I currently have a native plugin based on Napi in nodejs/Electron and I want to port it to support an existing CefSharp application. The extension has performance critical parts and relies on direct access to things such as ArrayBuffers and therefore using CefSharp C# bindings is not feasible. From looking at the CEF V8 API it shouldn't be that bad to port it from Napi to CEFV8 calls.
From looking at the code it seems that I should write my own CefSharp.BrowserSubProcess.exe based on https://github.com/cefsharp/CefSharp/blob/master/CefSharp.BrowserSubprocess/Program.cs and implement
IRenderProcessHandler
here. However,IV8Context
andV8Context
(https://github.com/cefsharp/CefSharp/blob/master/CefSharp.BrowserSubprocess.Core/Wrapper/V8Context.h) do not expose a native handle toCefV8Context
.I also looked at
CefRegisterExtension
, but that looked fragile and unsupported. It also doesn't have life cycle hooks.I think adding something along the lines of
UIntPtr GetNativeContext(){return _context.get();}
toV8Context.h
would solve my use case. Or is there maybe some other way to access CEFV8 without forkingCefSharp.BrowserSubprocess.Core
?Beta Was this translation helpful? Give feedback.
All reactions