4 ms·

Is there a reason you chose not to build / refactor the project as a library to call from Python?

• jakogut 7y ago
  Can you clarify your question? I'm using Cython to write extension modules that directly interface with CEF's C API. CEF is about 40k lines of C++ that programmatically controls Chromium, which itself is written in C and C++.
  • ratboy666 7y ago
    Email me at fred(underscore)weigel(at)hotmail(dot)com I interfaced CEF to Java in 2000 lines of C++ Simple, easy API. I run CEF in a separate process, and use the Window manager (Linux and Windows) to cause the Chrome windows to overlay the application windows. Standard pipes are used between the controlling process and CEF. Email me if you are interested. As a ps -- I can use CEF from shell scripts as well. Anything with a C FFI works. FredW
  • jessermeyer 7y ago
    I see. Thanks, that does change my understanding of your situation. My revised question with your clarifications in mind is, is there a reason you're not calling CEF's C api directly from Python? Are your extension modules doing some heavy lifting themselves, or are you using Cython just to handle the glue between the language interface?
    • jakogut 7y ago
      > is there a reason you're not calling CEF's C api directly from Python? Such as by using CFFI? Cython's strength, in my opinion, is in the fact that it is its own language resembling both C and Python that compiles to down to C, rather than just an FFI. > Are your extension modules doing some heavy lifting themselves, or are you using Cython just to handle the glue between the language interface? I would say the majority of the application logic is written in plain Python, and Cython makes interfacing with it, creating higher level interfaces, and marshaling data far easier than with CFFI or using the C API directly. This is pretty subjective though.