This is generally an improvement over the initial GtkLabel approach:
- Multiple definition lines can be selected at once.
- The widget doesn't keep a selection caret around (which means
it can't be controlled from the keyboard, a conscious trade-off).
- Text doesn't needlessly go to PRIMARY immediately during selection,
making it somewhat possible lift the self-exception for
the PRIMARY selection watch.
Closes#2
- Install a link to sdgui to the Start Menu.
- Associate the .ifo file extension with sdgui.
- Change the installation directory name to contain a space,
rather than a dash, since that appears to be the norm.
It's also copied over to the display name.
And thus, the GUI has become somewhat usable on Windows.
Remove most unused Adwaita icons and cursors, it's about 30 mebibytes
of raw bullshit that doesn't seem to be missing in any shape or form.
Rather sadly, the script is too complex to be rewritten in CMake script.
Nothing in GTK+ appears to be suited for what are virtually infinite
lists. Our workaround with GtkLabel and GtkScrolledWindow has been
heavily suboptimal and needs to be replaced.
Use Pango directly to handle our relatively simple needs.
Upgrades:
- the widget can be scrolled,
- keywords are repeated for each definition line,
- definition lines are now wrapped, and support 'g' and 'x' fields.
Downgrades:
- text can no longer be selected, so far.
Writing DocBook XML by hand is an awful experience and the tools aren't
much better. Asciidoctor does it well. There's no need to worry about
semantics, man(1) just needs to be able to show something at all.
This project's manpage is sadly almost useless right now.
As it happens, there is no real need to constantly poll for changes,
since XFixes can inform us of updates as they happen.
With GTK+ gone we've got dependencies and error handling under control.
XCB is a truly awful thing to learn, though.
Our method will never work on Wayland or Windows, so we don't miss out
on anything by abandoning the huge toolkit.
I've come to the conclusion that copyright mostly just stands in the way
of software development. In my jurisdiction I cannot give up my own
copyright and 0BSD seems to be the closest thing to public domain.
The updated mail address, also used in my author/committer lines,
is shorter and looks nicer. People rarely interact anyway.
