Is there documentation on how to create and publish Dolphin service menus so they will appear in Dolphin's "Download New Services" list?
There's https://store.kde.org and dolphin service menus there usually have install.sh and deinstall.sh scripts (names vary though, e.g. some have 'install-it.sh'). Is that a thing? Just to be sure I want to see official documentation.

Why kde4 service menus are available for downloading via kde5 dolphin? Are they still supported? I think they are not, since new downloaded menus appear in kde4 krusader, but not in kde5 dolphin.

FreeSlave wrote:Is there documentation on how to create and publish Dolphin service menus so they will appear in Dolphin's "Download New Services" list?
There's https://store.kde.org and dolphin service menus there usually have install.sh and deinstall.sh scripts (names vary though, e.g. some have 'install-it.sh'). Is that a thing? Just to be sure I want to see official documentation.

Why kde4 service menus are available for downloading via kde5 dolphin? Are they still supported? I think they are not, since new downloaded menus appear in kde4 krusader, but not in kde5 dolphin.

KDE Service Menus documentation

Old, needs update: Development/Tutorials/Creating Konqueror Service Menus - https://techbase.kde.org/Development/Tu ... vice_Menus


Get Hot New Stuf

The KDE Is using GHNS - http://newstuff.kde.org:

What is this about?

The 'Get Hot New Stuff' slogan refers to the ability of KDE applications to download data and extensions, and provides users with the possibility of sharing their creations with the rest of the world. KDE Data Repositories host such data for a number of KDE applications

Third party - Opendesktop.org

Everyone can upload their creations to share.

History:
- openDesktop.org. 15 years in review: http://karlitschek.de/2016/01/opendeskt ... in-review/
- openDesktop.org changes: http://karlitschek.de/2016/01/opendesktop-org-changes/

Under new owner: https://forum.opendesktop.org/t/welcome ... rg-forum/8

As most of you might have noticed, we are in the middle of transitioning opendesktop.org stores to new servers and also a new backend. All product, user and comment informations should be preserved. All login accounts are kept. If you experience any issues to login to the new servers, please post here or send us an email, we're watching out for your feedback and listening. Note that if from time to time some categories or products may not showing up temporarily, don't panic, as everything is being saved and evaluated to be made available again. One of the biggest transitions will be kde-look.org, which will take the most time, since OD resources are tightly integrated into Plasma's GHNS service. The whole transition could take up to another 12-15 weeks. One of the first features of our new backend is a new mutiple files upload service, which should eleminate the need for posting links to 3rd party storages....

KDE Software Store - https://dot.kde.org/2016/09/03/kde-software-store

In January 2016, Blue Systems acquired hive01 from Frank Karlitschek and restarted work on openDesktop. Since then, content has been cleaned up, the server backend has been replaced by a more modern and scalable solution,...

Bug reports

A wish: Bug 281517 - Standard way for Service menu installation - https://bugs.kde.org/show_bug.cgi?id=281517

The Dolphin is using ruby script to install and deinstall Service Menus.

---------------------Note ! ---------------------------
Fixed with: https://cgit.kde.org/dolphin.git/commit ... 0880bc3a1a

Looking Dolphin 16.08.2 /usr/bin/servicemenuinstallation
and /usr/bin/servicemenudeinstallation and finding that they are still using KDE4 paths. Filing a bug report: Bug 371907 - Dolphin, KDE Framework, service menu installation and deinstallation ruby scripts are using KDE4 paths - https://bugs.kde.org/show_bug.cgi?id=371907

---------------------Note ! ---------------------------




Summary

- There is an old Service Menu doc for the KDE4. It can be used as a template for the KF5

Service and the Service Menu paths are:

Code: Select all

$ kf5-config --path services

=>
~/.local/share/kservices5/ServiceMenus/
and
/usr/share/kservices5/ServiceMenus/

- GHNS Service Menus are downloaded from the third party data source.
- There is no safeguard. No one is checking before a user if the Service Menus are good or bad or even malicious.
- The installation is executed by a ruby script.
- There is no standard (KDE) way to build a installation script.
- The simplest, Single-File Service-Menu, is still using KDE4 paths. Note ! Fixed with: https://cgit.kde.org/dolphin.git/commit ... 0880bc3a1a
- There can be installation scripts. The servicemenuinstallation ruby script tries to parse them:

Code: Select all

/usr/bin/servicemenuinstallation:
...
# try: install-it.sh
# try: install-it
# try: installKDE4.sh
# try: installKDE4
# try: install.sh
# try: install
...

--------------------------------------------------------------

Added note of the fix of the Bug 376922 - Don't show new Service Menus in KDE Store - https://bugs.kde.org/show_bug.cgi?id=376922

Thanks for detailed response and sending bug report.

So the thing is kinda broken now because of moving kde-look.org to store.kde.org (Dolphin still downloads old servicemenu versions from kde-look.org era and does not see the new ones) and kde5 dolphin still using kde4 paths.

Documentation needs to be updated and adjusted to KDE5 too. I think external services and the way how installation script works should be explicitly stated. There also should be a declared way for servicemenu authors to differentiate when their install scripts are called for kde4 or kde5. Or they can just install both versions checking if kde4-config and kf5-config are available. Either way it should be mentioned in docs.

Rog131 wrote:KDE Service Menus documentation

Old, needs update: Development/Tutorials/Creating Konqueror Service Menus - https://techbase.kde.org/Development/Tu ... vice_Menus

The tip about using shell is somewhat misleading and even dangerous, since using field codes (like %f) inside shell script may lead to interpreting file name as shell code.