I mean embedding into applications. There was no documentation or guide for embedding it into anything last I checked and this is just a demo browser that’s being released. If embedding it into applications is as hard as Gecko, it will have no chance against Blink and WebKit.
If you’d like to embed Servo in your own application, consider using tauri-runtime-verso, a custom Tauri runtime, or servo-gtk, a GTK4-based web browser widget.
to use Tauri: sure, pull in a huge other project to be able to use our project 🫰
use GTK: again, pull in a bunch of unrelated dependencies to be able to embed our project
I can’t give servo some graphical surface (OpenGL, Vulkan, Metal, DX, whatever), call a function to open a webpage and see it draw on that surface. There’s no lib with documentation on crates.io, no bindings for other languages, and non of the things I mentioned in my previous comment.
It feels like this is built just like Gecko was for Firefox: single consumer with the consumer being the “reference implementation”.
There was no documentation or guide for embedding it into
This is what you posted
If you’d like to embed Servo in your own application, consider using tauri-runtime-verso, a custom Tauri runtime, or servo-gtk, a GTK4-based web browser widget.
Great documentation and exceptional guide! 👏 What next, are you going to tell me that the code is the documentation? “Just read the code”?
I mean embedding into applications. There was no documentation or guide for embedding it into anything last I checked and this is just a demo browser that’s being released. If embedding it into applications is as hard as Gecko, it will have no chance against Blink and WebKit.
https://book.servo.org/
“Tauri” you say?
So, in order to embed Servo you need:
I can’t give servo some graphical surface (OpenGL, Vulkan, Metal, DX, whatever), call a function to open a webpage and see it draw on that surface. There’s no lib with documentation on crates.io, no bindings for other languages, and non of the things I mentioned in my previous comment.
It feels like this is built just like Gecko was for Firefox: single consumer with the consumer being the “reference implementation”.
This is what I said
This is what you posted
Great documentation and exceptional guide! 👏 What next, are you going to tell me that the code is the documentation? “Just read the code”?
I also provided a link, which will lead you to the documentation.