Bug 411198 - Implement Klipper Actions repository for easy searching and installing action scripts
Summary: Implement Klipper Actions repository for easy searching and installing action...
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard widget & pop-up (show other bugs)
Version: 5.15.3
Platform: Other Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-23 09:11 UTC by Murz
Modified: 2023-05-17 00:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Murz 2019-08-23 09:11:56 UTC
Klipper have very cool Actions feature! Via actions we solve many popular tasks:
- convert text encoding
- make calculations
- do urlencode/urldecode for string
- convert timestamps to human readable date
- detect postal address and link to google maps
- detect phone number and initiate call
- and more other...

But creating new actions for not-improved users are too hard task! Especially understanding regular expressions, and write needed command to execution.

For solve this problem, will be good to implement Klipper Actions repository, where users can list of ready actions, easily install/uninstall them.

Here is example of Krusader actions repository:
https://store.kde.org/browse/cat/372/order/latest/

Some other KDE software already contains repositories for installing features:
- Dolphin Add-On Installer
- Kate plugins
- Plasma themes and colors

So, why not to do same Actions repository for Klipper too? 

First easy step can be creating public user repository on store.kde.org website for manual adding/downloading, like this https://store.kde.org/browse/cat/372/order/latest/

And great second step will be integrate them in Klipper configuration tool!

What do you think about this idea?
Comment 1 Nate Graham 2023-05-17 00:33:12 UTC
It's a cool idea, but given the lack of movement for so long, I think this is unlikely to be implemented unless someone submits a merge request to do it. Accordingly, I'm going to close this request so that the list of requested features better reflects work in progress or under active consideration. This doesn't mean that the idea is being vetoed, just that there aren't resources to consider implementing it absent volunteer contributions to do so--for which no formal feature request is needed. Thanks for understanding!