Sun, Jul 21
The changes have all been implemented.
Mon, Jul 1
Jun 22 2019
@ngraham: I wasn't aware that gwenview ships some KIPI plugins of its own, but here (Debian sid), the remaining KIPI export plugins are still listed in gwenview.
I'm not sure what you mean by "has no way to install them" - the general design of KIPI did not try to install anything at runtime. Plugins are usually installed like any other package via package manager and the KIPI-enabled programs use whatever plugins are available.
Gwenview now gained Purpose support, so from my POV KIPI can go
Gwenview has a way to install the Kipi plugins that's been semi-broken for years so I doubt there are many or any users left. Spectacle shows them if already installed, but has no way to install them. Don't know about KPhotoAlbum. The last I checked, many of the Kipi plugins didn't actually work. And some are now redundant, e.g. Purpose can send via email too.
Apr 14 2019
Removed in 281f7a18c9bd9a05b3401826261b7d85e78bdd57
The feature has been implemented and merged to master. See 3fe442065776ad905b141d429908dfbab6928f66
Apr 7 2019
Kipi is dead. Long live purpose!
Feb 25 2019
To the best of my knowledge Gwenview doesn't use Purpose. I once looked into adding it since it would make sense.
Feb 24 2019
Spectacle can use both purpose and kipi-plugins in its Export menu/button.
Feb 15 2019
Update: there's now DB::UIDelegate which helps breaking dependencies on MainWindow/KMessageBox.
Feb 7 2019
Jan 21 2019
Jan 16 2019
Oct 27 2018
I've implemented a proof-of-concept for something similar in the branch feature/categoryDates: In this branch, the date range for categories is displayed, and it is possible to sort by start-date...
Oct 14 2018
As it turned out, support for Qt < 5.8 has been dropped intentionally.
Oct 7 2018
Here are my personal notes on this so that they don't get lost:
Sep 9 2018
Sep 4 2018
Sep 3 2018
Aug 13 2018
So far, I'm explicitly vague - I've been sitting with Nate earlier today and he mentioned that gwenview could possibly improve in the use-case "tagging" and suggested that I should just open a task if I'm interested.
Hi, thanks for reaching out.
Jul 13 2018
Well I actually didn't see the line above at first. Thanks for the correction
Jul 12 2018
Oh dear, you're right. Should've looked at the whole picture...
Also note the big elephant in the room: the typo is not in the British English translation, but in the original text...
I just pushed 812910752712f185e5ef19bf4786346217232475 to fix it, which will invalidate all the translations (so Steve will notice it by tomorrow).
I've forwarded the information to the translator...
@pino Thanks for the hint - I wasn't aware that the translations in git are a one-way street...
Note that translations are handled by an automatic system (informally called "scripty") that extracts messages from all the translatable resources, like messages in the applications/libraries, and also strings in .desktop (and alike), and .appdata.xml files.
As such, editing translations directly is not a good idea, and indeed scripty reverted to the string actually in the en_GB translation the day after this commit.
Please contact the British English team, or the translator directly:
Sure thing - ship it!