Ultralight VS vingester

[2] https://ultralig.ht/

Web rendering would be Blink, with V8 being the JavaScript engine. I believe they have their own UI rendering process.

I know of another company that does something similar for the UI process, but with WebKit instead as the base:

https://github.com/ultralight-ux/ultralight#rocket-dual-high...

What I'd really like to see with CEF et al, is JS being dropped, in favor of directly controlling the DOM from the host language. Then we could, for example, write a Rust (or Kotlin, Zig, Haskell, etc) desktop application that simply directly manipulated the DOM, and had it rendered by a HTML+CSS layout engine. Folks could then write a React-like framework for that language (to help render & re-render the DOM in an elegant way).

Ultralight (https://ultralig.ht/) looks pretty cool. I think another possible option is Servo (https://github.com/servo/servo) – it was abandoned by Mozilla along with Rust during their layoffs a while back (but the project still seems to have a decent bit of activity). It would be great if some group of devs could revive the project, or a company could fund such a revival.

Eventually, we'll need to reflect on, and explore whether HTML+CSS is really the best way to do layout, and we could maybe perhaps consider proting the Android/iOS layout approach over to desktop.

I'm curious if the project will be open-source or do you have plans to go the Awesomium/Ultralight route with both open/closed sources and volume licenses? Or do you plan to offer commercial support services like other open source software?

I’m not tied to any language, but it needs to be able to wrap a c++ library. I started with .NET 7 MAUI - no linux support & very mobile focused. Tried out Electron. Wins on ease and usability, but has massive overhead. (Basic “Hello world” executable compiled to over 200mb) I then discovered Ultralight (https://ultralig.ht/). Big win on size, but was last updated 3 years ago.

tauri exists or if you wanted to ultralig.ht

I agree web stuff is really the best way to develop UIs. Good luck making responsive stuff in C++ for example. The paradigm of HTML, CSS, and JS is extremely powerful and even allows you to use canvas, webgpu, wasm.

There are multiple commercial projects that use web dev paradigm for GUIs:

https://coherent-labs.com/

https://ultralig.ht/

https://sciter.com/

Nice review, thanks! There are also: Ultralight (based on Webkit), LiteHTML, Tkhtml3 and Lobo Evolution. See also timeline of web engines.

Another consideration is, if you are usually capturing the exact same web page (like perhaps a stream elements overlay or similar) is to use Vingster.app (free and open source) which says it also works for Mac.

I use: https://vingester.app/ (free)

there is Vingester if that's something you do often but I find that I'm doing a lot of that work with a browser source inside OBS now

also don't do anything else on your computer while recording, and I'd recommend using something like (free) Vingester to make it easier to capture the window.

You could use an app like https://vingester.app/ to create an NDI stream of each page and convert those to SDI using the many Birddog/magewell/Kiloview options.

I work overlays in streaming with SPX-GC (https://github.com/TuomoKu/SPX-GC) which feeds HTML via a virtual server and read those with Vingester (https://vingester.app/), a headless browser, to NDI. There are other tools that do this for framesharing like SPOUT (https://ultralig.ht/) and pretty sure something for an apple variant (Syphon has been suspended, right?)

I found the soluction which works really, i mean - REALLY - good. On mixer side I use Vingerster https://vingester.app/ to get the video (it can emulate OBS, which i required to get data from Ninja). Vingester outputs the video to NDI and that I can get the stream to OBS on main mixing comupter. The video is flawless, no jagging.

You can also just capture the desktop-audio or use https://vingester.app/ (vingester) to capture audio/video from VDO.Ninja. Apps like Vmix and probably Manycam support VDO.Ninja, and would also I'd imagine bypass the problem, rather than using OBS directly for browser capture.

So, I've been using VDO.Ninja and Vingester to pull WebRTC live video from anyone using the Chrome Browser and into a wireframed OBS Studio environment for my live production, and it works beautifully. The issue though is I have a client that wants something more "user friendly" for guests - and they are willing to pay for it. I've been doing some research, and I see Cicso Webex a lot.

Since I first started to put together this workflow, I've been revising it to make it leaner and more robust. I wanted to share the latest iteration of this guide - one that uses the Vingester + OBS Window Capture method for my sources, as well as some great plugins I've come across.