Changed how we extract build targets in Builder. If your project uses Flatpak, things should mostly just work (even if using, say, CMake). Here is Elementary's Code (scratch) running as a Flatpak built by Builder, using Builder's debugger, (which even works with Vala-based sources). https://mastodon.social/media/wX_4Rmxt75Ygmu_JwgA
Curious if people think integrating user docs w/ API docs like this is worthwhile.
The major difficulty in including API docs w/ deps is that it massively grows the file-size. So I'll have to come up with something clever to make them non-giant in downloads.
(Roughly 22mb compressed, 300mb on disk).
Putting together a new tool to allow embedding GNOME documentation into Builder's docs so that API docs can cross-reference.
I can't stand giving gtk-doc to end users, so I've been using Sphinx.
Over the last day or two I've joined my templating library (an AST, interpreter, and can call into Gobject Introspection) and my C parser-generator for rng files to get a .gir parser.
Now I can generate docs from .gir files for C.
If you want developers of software you use (or hate for whatever reason), try not being abusive and maybe they'll listen to your criticism instead of leaving the forum.
Deleted my reddit account, feels better already! I'm sick of that toxic shithole.
Think I'll do some more live hacking tomorrow on twitch. Sort of annoying because it still requires running X.
It will be in upcoming nightly builds, but does require Wayland for proper multi-blob detection and gesture recognition.
A post on some of my thoughts for a modern editor design given what we can do in Gtk4 and a new data-structure I designed.
Still write desktop Linux applications in C/gtk+ like me? You might find this helper in libdazzle useful.
Headed up to Seattle for SeaGL tomorrow night.