I did a side-by-side comparison of this zbitx repo and the farhandev branch of sbitx. ?They look suspiciously similar, with some newer changes brought in, but it looks like it’s still clearly meant for sbitx. ?All the strings still say sbitx. ?So this is not really what you are shipping, is it? ?If we look at git log:

there is only one recent patch, addition of the schematics. ?(Thanks for that!)

The more similar it is, the easier it is to keep working on patches for both zbitx and sbitx at the same time. ?But I would think you would factor out the things that are different into as few files as possible, if they continue to be that similar. ?

I am working on some patches, trying to separate the frontend from the backend so that other UIs are possible. ?So I wanted to see whether I can easily apply them to both code bases. ?But it’s hard to believe that you are going to routinely run a version with?sbitx_gtk.c as-is, considering that your display is now an Arduino project connected over a slow channel, not an X server, and can’t show the GTK-based UI. ?Of course that UI is still useful if an HDMI monitor is attached, or for remote-X11 use over the network; but not so much on the zbitx as it ships? ?So my goal is to eventually have a radio daemon with no UI, and separate UI processes as needed. ?I think we both have the same problem: GTK is not useful if you don’t want to see that UI anywhere, and yet it’s hard to remove. ?I figured maybe you started to take some steps in that direction.