Ultralight
skrift
Ultralight | skrift | |
---|---|---|
53 | 4 | |
4,597 | 9 | |
0.3% | - | |
2.9 | 6.8 | |
15 days ago | 9 months ago | |
CMake | Ruby | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Ultralight
- Ultralight: Display Web-Content Everywhere
-
Writing a TrueType font renderer
[2] https://ultralig.ht/
- This year in Servo: over 1000 pull requests and beyond
-
Arc browser launches its Windows client in beta
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...
-
Ode to the M1
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.
-
Anselm's Jazz Distributed Infrastructure Framework
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?
-
Best cross-platform (Win, Mac, Linux) desktop frameworks?
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.
-
Remember when this was 0% and 70 mb? This is comical.
tauri exists or if you wanted to ultralig.ht
-
Digital Audio Workstation Front End Development Struggles
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/
-
what do you think about alternative browser engines?
Nice review, thanks! There are also: Ultralight (based on Webkit), LiteHTML, Tkhtml3 and Lobo Evolution. See also timeline of web engines.
skrift
-
Writing a TrueType font renderer
https://github.com/vidarh/skrift
Libschrift is very readable.
I did my Ruby rewrite basically just top to bottom before reorganizing it. Mine is... readable if you're well versed in Ruby, but still has some warts where it's less than idiomatic Ruby because I stuck closely to the original.
Basically TTF has a crufty binary format, but the basic font data if you're willing to ignore ligatures, hinting, OpenType support and emoticons, is fairly simple (it's basically a bunch of polygons consisting of quadratic beziers and lines, and quadratic beziers are easy to tesselate into lines if you don't want to do a more complex curve renderer), just error-prone to figure out.
If you want/need OpenType you need to support cubic beziers on top of that, which isn't that bad. If you want to support emoticons you need to support a subset of SVG (!)...
So TTF without those bits is pretty much the halfway point.
Also do look at the Canvas C++ header implementation linked in this comment[1]. It's readable, and more featureful than libschrift or my Ruby rewrite, and it's still small while packing a full rendering library in there not just the font renderer. I intend to pillage it (with credits) for ideas ;)
[1] https://news.ycombinator.com/item?id=38839114
-
I Love Ruby
I've put plenty of half-baked stuff out there over the years, so that doesn't really worry me. More that at the moment if you try to copy any of it the github repos are all at different stages of not quite up to date, and APIs are in flux, and you're just really likely to have a bad time trying to get anything to work.
I think the real starting point for me is going to be to clean up PureX11 a bit more so the API is at least somewhat cohesive, and then push the WM as it's working enough that it's been my only wm for a few weeks (it does have significant quirks still, but with somewhat minor cleanups it's a decent starting point to play with), and then the terminal as it's fairly freestanding, then some of the file management tools, toolbar, popup menu etc., then lastly my editor. The editor has by far changed most from the version on Github and is also most likely to cause problems for others, so that might take a bit of time, not least because I'm in the middle of a fairly significant overhaul of the way the views and models works.
Here's some of what is out there, though:
* Skrift: This is a Ruby port of libschrift, a TTF font renderer. It's heavily cut down, and currently stands at about 680 lines of code. I intended to tidy up the API as it's still a bit messy after my rewrite: https://github.com/vidarh/skrift
* X11 bindings for Skrift: https://github.com/vidarh/skrift-x11 - these are messy, and I have significant updates to them (including basic fontset support and a mechanism for pixel-perfect boxdrawing characters at any reasonable scale) that have not yet been pushed: https://github.com/vidarh/skrift-x11
* Pure-X11: This is a form and significant overhaul of pure X11 client bindings for Ruby (as in not Xlib or XCB needed): https://github.com/vidarh/ruby-x11 - it's not terribly out of date, but it's a bit in flux as I don't like the initial mechanism, used for the protocol and so I'm thinking about how to trim it down and make it easier to use.
* This is the starting point for my terminal. My terminal is nothing like that any more, but this is the repo that will get all the updates, eventually: https://github.com/vidarh/rubyterm - this initial prototype used a C extension and server-side fonts, while the current version uses Pure-X11 and Skrift
* This was the very first version of my WM I used, a few hours into the switch (from bspwm). It's a straight port from TinyWM. My current one has tiling and some EWMH support and multiple desktops and adds about 700 lines of code - it'll start appearing on Github soon: https://gist.github.com/vidarh/1cdbfcdf3cfd8d25a247243963e55...
* This is a script I used to feed into a 9menu style popup menu script from my file manager to generate folder-contextual actions based on the folder contents: https://gist.github.com/vidarh/323204137de5293bfe216ec751646... -- the current version is quite a bit slicker and will eventually show up
* This is a very dated and broken version of my editor, and odds are you'll struggle to get it to work at all, as it depends on various helper scripts that are not yet packaged up, as have been massive updated since that version; I'm hoping to maybe bring the repo a bit more up to date over the holidays: https://github.com/vidarh/re
* This is a gem that handles the input processing: https://github.com/vidarh/termcontroller
* This does keyboard mapping from symbols from termcontroller to higher level user-defined sequences:
-
Write Your Own Terminal
No current version, but I'm preparing it. But actually, to see a really ridiculously minimalist start, this was my starting point, which used a tiny X extension to do the X rendering (though it optimistically included a dummy class intended to be the start for the Ruby X backend). It's awfully limited, and awfully broken, but it shows how little it takes to be able to start writing:
https://github.com/vidarh/rubyterm
It's totally useless for anything other that testing or expanding on, but it was the starting point for the terminal I now run every day, and I'll be updating that repo as I clean up my current version at some point.
The current version uses this for a pure Ruby (no Xlib) X11 client implementation:
https://github.com/vidarh/ruby-x11
And this pure-Ruby TrueType font renderer (I did the Ruby conversion; the C code it's based on was not mine, and is a beautiful example of compact C - look up libschrift):
https://github.com/vidarh/skrift
What are some alternatives?
webview - Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
bubbleos
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
rouge-gtk_theme_loader - Load GtkSourceView themes into Rouge (Ruby syntax highlighter)
qt-ultralight-browser - Ultra-lightweight web browser based on Qt Ultralight webview, powered by Ultralight HTML renderer
crt - Minimal terminal emulator for Bubbletea.
wry - Cross-platform WebView library in Rust for Tauri.
ruby-x11 - Pure Ruby implementation of the X Window System Protocol
ClassicUO - ClassicUO - an open source implementation of the Ultima Online Classic Client.
skrift-x11 - Pure X11 integration for the pure Ruby "Skrift" TrueType engine
litehtml - Fast and lightweight HTML/CSS rendering engine
keyboard_map - A small Ruby gem to map keyboard escape sequences