-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be great to have a prebuilt distribution that's easily embeddable #52
Comments
node-webkit is not designed for embedding, and we even don't have public interface to do that. Maybe you would be interested in cef, which is designed for embedding a browser window in third party applications. |
@ZECTBynmo , it's hard to redesign the whole project and make it embeddable, but there is another way to use node-webkit with your C++ code: make your C++ code a node module then it should run on node-webkit. |
Thanks for the responses. I've been looking at cef at your recommendation, the appjs implementation in particular, and it seems like a solid course. Thanks for the help! Unfortunately I can't run my application as a node module, otherwise that would definitely be the path of least resistance. |
Moving forward with CEF you might want to pay attention to CEF3, which is multi-process and aligns with the up-to-date chromium architecture. AppJs is still with CEF1 IIRC. -------- Original Message -------- Thanks for the responses. I've been looking at cef at your recommendation, the appjs implementation in particular, and it seems like a solid course. Thanks for the help! Unfortunately I can't run my application as a node module, otherwise that would definitely be the path of least resistance. Reply to this email directly or view it on GitHub: |
Thanks for the tip! |
I would really like to embed node-webkit into my C++ application. As I understand it, the only way I can embed node-webkit into my solution would be to build it from scratch. It would be great if there was a prebuilt distribution that I could embed easily without building the entire webkit chain.
The text was updated successfully, but these errors were encountered: