Support for Flatpak

[Sesivany]

In order to use JSignPdf on Silverblue, I've created a flatpak of it. I'm planning to submit it to Flathub, so that it can be used by other users. But before I do that, I'd like to ask if the project would be willing to adopt Flatpak as an installation format (one build works on all Linux distributions). It's about shipping several files with fairly low maintenance. Having JSignPdf on Flathub is about maintaining one GitHub repo with the manifest. The advantage of the Flathub flatpak being maintained by the project itself is that it gets the verified status (many distributions only show verified apps by default).

For the flatpak I had to create the following files:

net.sourceforge.JSignPdf.metainfo.xml - AppStream metadata (useful not only for Flatpak)

- high-res icon, the original one is 48x48, Flathub requires at least 128x128. The icon has been redrawn by AI.

net.sourceforge.JSignPdf.txt - Flatpak manifest

I thought I'd create a ticket first to see if there is any will to adopt this and in what form before I create a pull request.

[kwart]

Hi Jirka, sorry for the late answer. The direct Flatpack package support sounds good 👍
Let me look at it.

[kwart]

@Sesivany Could you create a PR with the Flatpak support files?

What I would suggest in the PR:

• replace sourceforge.net naming with GitHub one (App ID, project URLs, download link); for instance com.github.intoolswetrust.jsignpdf (or io.github.*)
• put Flatpak-related files to /distribution/flatpak subdirectory
• put the metadata XML file in the /distribution (or do you think, project root is a better place?)

If you think something should be handled differently, please comment. I've never used the Flatpak before 😅

[Sesivany]

Hi,
Flathub requires io.github.* for Github-hosted projects, so I propose io.github.intoolswetrust.jsignpdf.
I'll put the Flatpak-related files to /distribution/flatpak as you say.
I've also noticed that the project doesn't ship a desktop file, it's required for any desktop app on Linux, but not Flatpak specific, so I'll put it in the /distribution together with the metadata XML.
BTW how about the the icon? Is it something you would be willing to adopt as a new hires icon or should I just ship it among Flatpak-related files? Because Flathub requires the icon to be in a higher resolution than what the project ships.

[kwart]

Sure, I like the improved 512px icon. 🙏 Let's use it where it makes sense.

Windows build uses distribution/doc/icon/icons.ico with layers containing the icon in different resolutions. We can regenerate it to include a 256x256 px version as well. (Current highest res is 128x128 - you can see it in the icons.xcf file too).

[Sesivany]

I've created a pull request: #309

I didn't notice files that could provide an icon in a better resolution. I could have saved time. However, the redrawn icon has some benefits. I have it in 2048x2048, the resolution that ought to be enough for everyone, but it'd be good to find a way to vectorize it.