My application allows you to have a quick preview of files in folders and I aim to integrate it as much as possible with the Dolphin file manager (similar to Quick Look/View or Gnome sushi). For now it’s in Qt5 but I intend to port it to Qt6 when I have the time.
For now it’s on Github but I know it should be published on invent.kde.org and that’s what I will do in the near future if there is a possibility of making it an official application.
I have read several sources but I still have doubts about how I should proceed to have a first test version that I can share with other users via the repositories.
Questions:
Can I add the translation for my native language without having a translation team?
Can I use the domain name org.kde.kiview for the flatpak package to be published on Flathub even though it is not currently an official application?
The way my application integrates with dolphin (due to dolphin’s technical limitations), and the way documents (xlsx,docx,odt,etc) are displayed looks more like a hack, will this prevent my application from becoming an official application?
How do I publish to Flathub if I have to put the project on invent.kde.org?
This would be coordinated with the main internationalization team to migrate your existing translations (Italian) to the new infrastructure.
You mean you plan on publishing it on Flathub before finishing incubation?
That page was already updated to mention the new method. Just add a Gitlab CI file to start building a flatpak, and once you’re happy with it, you can request to sign it.
I’ll update the tutorial page to not have the name “kdeapps” anymore since it’s misleading.
The same way you’d do it normally. You submit a manifest, get it reviewed, then merged. The difference is that once it’s finished, the KDE Team on Flathub gets added together with you as collaborators.
Nightly flatpaks are built via Gitlab CI in KDE infrastructure, Flathub packages are built via Flathub buildbot. All you need to care about as a developer is to have a working manifest and make sure the CI builds finish ok.
You mean you plan on publishing it on Flathub before finishing incubation?
Previously I didn’t know how to publish a test version without using kdeapps and I was thinking of publishing on Flathub to do some testing and see if any changes are needed.
I’m pretty new to all this and I still need to figure out a few things.
That page was already updated to mention the new method. Just add a Gitlab CI file to start building a flatpak, and once you’re happy with it, you can request to sign it.
I apologize, I didn’t realize the documentation had been updated.
