Stephan Sokolow

TBH I'd love to see a Qt GUI for MComix. We'll see how things unfold. Right now, I'm still clearing out a large backlog of "TLC needed" for hobby projects tracing back to when time management problems I was already having were exacerbated by COVID bursting onto the scene. As such, any MComix stuff is considered "less than ideal, but it works, so focus on the things that are broken or de facto abandoned". Not sure if PyQt is a better choice than Qt for Python, now that it has official support in Qt6....

TBH I'd love to see a Qt GUI for MComix. We'll see how things unfold. Right now, I'm still clearing out a large backlog of "TLC needed" for hobby projects tracing back to when time management problems I was already having were exacerbated by COVID bursting onto the scene. As such, any MComix stuff is considered "less than ideal, but it works, so focus on the things that are broken or de facto abandoned". Not sure if PyQt is a better choice than Qt for Python, now that it has official support in Qt6....

Why is it a choice between (a) the MComix devs making the change in the project; and (b) you making the change as a local patch you'll have to carry. Because my patchset for MComix would be "How can I rip out everything that has changed since the last Comix release with minimal effort?" (Less "helpful PR material" and more "a private GIMPshop to MComix's The GIMP".) (I'm one of those people who stayed on Comix, despite MComix being available, until the last supported month of the last Kubuntu LTS...

Easy mouse-driven "un-fullscreen"

Is there a command-line validator tool for the format I should use? Yes, but the upstream maintainership situation is... less than satisfactory and it's no longer in sync with the published spec. (eg. It'll reject valid <description> markup with confusing error messages and reject valid <url> types, among other things.) The fork you're supposed to use is available as: flatpak install flathub org.freedesktop.appstream-glib flatpak run org.freedesktop.appstream-glib validate <FILENAME> EDIT: They also...

Is there a command-line validator tool for the format I should use? Yes, but the upstream maintainership situation is... less than satisfactory and it's no longer in sync with the published spec. (eg. It'll reject valid <description> markup with confusing error messages and reject valid <url> types, among other things.) The fork you're supposed to use is available as: flatpak install flathub org.freedesktop.appstream-glib flatpak run org.freedesktop.appstream-glib validate <FILENAME> They also want...

Is there a command-line validator tool for the format I should use? Yes, but the upstream maintainership situation is... less than satisfactory and it's no longer in sync with the published spec. (eg. It'll reject valid <description> markup with confusing error messages and reject valid <url> types, among other things.) The fork you're supposed to use is available as: flatpak install flathub org.freedesktop.appstream-glib flatpak run org.freedesktop.appstream-glib validate <FILENAME>

Is there a command-line validator tool for the format I should use? Yes, but the upstream maintainership situation is... less than satisfactory and it's no longer in sync with the published spec. The fork you're supposed to use is available as: flatpak install flathub org.freedesktop.appstream-glib flatpak run org.freedesktop.appstream-glib validate <FILENAME>